incubator-ooo-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 121185] Rotated metafile looses rotation of gradient in presentation mode and in export
Date Tue, 09 Oct 2012 10:11:33 GMT

Armin Le Grand <> changed:

           What    |Removed                     |Added
                 CC|                            |

--- Comment #1 from Armin Le Grand <> ---
ALG: This is a problem. The presentation is (as known) based on metafiles
(still). The converted object is a graphic object containing a metafile (as
graphic content).
The graphic object and it's content is handled as primitives now, thus the
content of the graphic object gets rotated with the object (what is expected
from my POV and correct).
When preparing the Metafile the slideshow is requesting that constellation has
to be expressed as metafile (as long as slideshow is using metafile as base
data). This is done, but - as you know in the meantime - there is no
corresponding metafile representation to do this. This would be equivalent to
leaving out step (2) of the description. Thus, the gradient would be rotated,
but also applied to the bound rect of the rotated rectangle and thus look
The object rotation is currently not applied to the created metafile gradient;
this could be done, but still leaves the problem that the gradient *will* use
another base rectangle, the bound rect of the rotated rectangle.
There are even two ways prepared to get back from primitives to metafile (one
based on converting the primitives back to metafile (the default currently),
one using VCL method rotate on the existing metafile), for both the adaption of
the object rotation angle to the gradient rotation is missing.
The best way to fix this would be to change presentation to use primitives (A).
The maximum possible fix is to get the gradient's rotation adapted (B). There
is no way to get the same gradient due to old gradient restrictions (you know
these in the meantime).
A is too expensive, B is doable but not optimal.

You are receiving this mail because:
You are the assignee for the bug.

View raw message