To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=101734
------- Additional comments from [email protected] Fri Jun 12 17:40:10 +0000 2009 ------- AW: For the used transformation, the fix will be okay. The SvtGraphicStroke conent will be prepared in object coordinates. The used polygons (the line itself, a start and/or end of line) will be transformed using the ObjectToWorld transformation. This transformation does not contain scalings in the used case (and no unproportinal scaling, too). The scaling would have had to be taken into account for the LineWidth and the DashDotArray otherwise. Anyways, in cases of more complex transformations than translation and linear scale, it would be better to use the decomposition. This is not needed for the current possible cases, but just a note to remember this. Added debug test code to VOCOfDrawVirtObj::createPrimitive2DSequence to be able to experiment with more than a translation. It is no problem for visualisation, just for e.g. PDF export the old concept of putting stuff into SvtGraphicStroke is not sufficient; to describe the existing data, a transformation would have to be added to it. Checking in solution... --------------------------------------------------------------------- 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]
