To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=111235





------- Additional comments from [email protected] Tue May 11 15:37:33 +0000 
2010 -------
AW: Found the reason now, it's pretty complex. The new interpreter to translate
metafiles to sequences of primitives used in the decomposition implementation of
the Metafile primitive uses stacks to hold created primitives and a
PropertyHolder for the current status (replacement for OutDev state). Of course
a ClipRegion coming along the Metafile cannot be applied at the time
interpreting it; it needs to be remembered in the state, all MetaActions coming
have to be interpreted, and when the ClipRegion changes (or Metafile is at end)
the created primitives get embedded to the current ClipRegion.
All this is correct and works well, but the transformation (AKA MapMode for
Metafiles) used to interpret the ClipRegion at the point in time it gets used
may be wrong; it's no longer in the state when the clip action came along, but
may have undergone any stacked changes during interpreting the other content.

There are two solutions:
(a) Remember the Tranformation with each ClipRegion in the state at the time the
CLipAction comes along
(b) Trasform the ClipRegions when they come along immediately with the current
transformation

Of couse (b) is the better solution, but it requires complete usage of
B2DPolygons as ClipPolygons in the process. This includes MetaFile actions which
modify the current active ClipRegion. For this i still used the old Regions, but
already internally clipped against PolyPolygons. This is a good pint to change
all this to PolyPolygons...

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to