To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=108160
                 Issue #|108160
                 Summary|cairocanvas no longer builds in m69
               Component|gsl
                 Version|DEV300m69
                Platform|Unknown
                     URL|
              OS/Version|Unix, X11
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P1
            Subcomponent|code
             Assigned to|thb
             Reported by|thb





------- Additional comments from [email protected] Fri Jan  8 15:39:28 +0000 
2010 -------
So, with the changes from 264257:67ee0f599864 canvas/source/cairo no longer
builds; this was done alongside issue 105655 and fixes polygon stroking with
line join == none. 

The changes are ok generally, but a) break the build because
doPolyPolygonImplementation wants a B2DPolyPolygon instead of a B2DPolygon, and
b) kills textured polygons, the CanvasHelper::fillTexturedPolyPolygon passes the
texture for the boolean linejoin parameter.

I'd suggest reverting the changes from m68 to m69 as a master fix (verified that
here already), and I can then have a shot at fixing the line join thing in e.g.
thbfixes10, which touches canvas/basegfx a lot anyway. Patch will be attached in
a minute, note that it needs to be reverse-applied (-R).

---------------------------------------------------------------------
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