Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 4.2.1
-
Fix Version/s: 4.2.2
-
Component/s: Core/Parsing
-
Labels:None
-
Environment:any
Description
Common image handling is still a bit of mess, looking more like a spaghetti dish. Currently we only support masking on a case by case bases and as result don't don anything when it's encountered on jpeg image.
Hopefully some time can be spent re-factoring the Stream class into a few new class the handles imaging in more structured manner. It's a big task but well worth the effort given that the Stream class is pushing 3000 lines. I'll create a new bug for this as it will likely be a 5.0 task as it will fit in nicely with the new parsing and file reading models.
Back to the problem at hand. The main image is a black jpeg and a CCITTfax iamges is used as a mask which makes the image readable. Pretty simple fix just have to apply applyExplicitMask() .
Hopefully some time can be spent re-factoring the Stream class into a few new class the handles imaging in more structured manner. It's a big task but well worth the effort given that the Stream class is pushing 3000 lines. I'll create a new bug for this as it will likely be a 5.0 task as it will fit in nicely with the new parsing and file reading models.
Back to the problem at hand. The main image is a black jpeg and a CCITTfax iamges is used as a mask which makes the image readable. Pretty simple fix just have to apply applyExplicitMask() .
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion