Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 4.1.1
-
Fix Version/s: 4.2
-
Component/s: Core/Parsing
-
Labels:None
-
Environment:Any
-
Assignee Priority:P1
-
ICEsoft Forum Reference:
Description
Quite a bit of refactoring was done in 4.1.1 to remove some duplication in the image rendering pipeline. One of the duplications was related to the fact that we where scaling some image types more then once. In the document in question their is a rather large image 2150x3033.
The image scaling flag was introduced the amount of memory used for some large images. Another side effect is that it makes "large" image look pretty. In general Java2D doesn't apply any smoothing or anti-aliasing for images bit AffineTransformOp can b used to help with this effect. The image in question is now scaled 50% which improves the quality a bit but not as well as the double image scaling did prior to 4.1.1. I'll have to go back and try and figure out what the equivalent scaling metrics where between the two versions.
The image scaling flag was introduced the amount of memory used for some large images. Another side effect is that it makes "large" image look pretty. In general Java2D doesn't apply any smoothing or anti-aliasing for images bit AffineTransformOp can b used to help with this effect. The image in question is now scaled 50% which improves the quality a bit but not as well as the double image scaling did prior to 4.1.1. I'll have to go back and try and figure out what the equivalent scaling metrics where between the two versions.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Reverted back to a double scale mechanism. the Shapes class scalling seems to be important in insuring that the image gets "crisper" during the scale. It would be nice to revisit the issue in the future.