|
Quick Lists
|
|
Bug ID:
|
4979025
|
|
Votes
|
0
|
|
Synopsis
|
mapDestPoint() fails for "Rotate" of 90, 180, 270 degrees
|
|
Category
|
jai:implementation
|
|
Reported Against
|
1.1.2
|
|
Release Fixed
|
1.1.3-beta
|
|
State
|
10-Fix Delivered,
bug
|
|
Priority:
|
3-Medium
|
|
Related Bugs
|
6353938
,
5074619
|
|
Submit Date
|
15-JAN-2004
|
|
Description
|
mapDestPoint() fails for "Rotate" of 90, 180, 270 degrees.
|
|
Work Around
|
Use "Affine" operation instead with a transform defined by
AffineTransform.getRotateInstance(angle, xOrigin, yOrigin)
|
|
Evaluation
|
xxxxx@xxxxx 2004-01-15
Problem appears to be due to optimization in RotateCRIF and MlibRotateRIF wherein a rotation of 90/180/270 degrees is effected by transposition followed by translation. The result is that the rendering of the RenderedOp node is therefore a translation implementation so that the mapDestPoint() invoked on the node is forwarded to the translation and the rotation part is not included.
xxxxx@xxxxx 2004-01-16
According to the customer the error is not limited to 90X degrees.
The problem is in fact limited to 90, 180, and 270 degrees. The purported error for other angles was due to a defect in the test case itself (for 5074619).
Posted Date : 2005-11-21 22:33:57.0
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
|
