To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=100851
User aw changed the following:
What |Old value |New value
================================================================================
Assigned to|aw |hdu
--------------------------------------------------------------------------------
------- Additional comments from a...@openoffice.org Tue Apr 7 11:18:31 +0000
2009 -------
AW->HDU: All mentioned basegfx polygon operations are quite linear;
clipPolyggonOnRange clips against a rectangle by clipping against the four sides
(clipPolygonToParallelAxis) and only linearly processes the polygon, so in the
methods listed above is no O(n^2) candidate at all.
All of this methods are used in Your imlementation of painting a PolyPolygon
using a XRender extension (X11SalGraphics::drawPolyPolygon), as preparation to
the trapezoid decomposition. There MUST be a cheaper way to paint AAed
polyPolygons on XRender, i hope.
As i already told You, the tremendous amout comes from the fat line geometrical
preperations (see case PRIMITIVE2D_ID_POLYGONSTROKEPRIMITIVE2D in
drawinglayer/source/processor2d/vclpixelprocessor2d.cxx). This does not make the
difference, since exactly the same primitive geometry is feeded to VCL when AA
is switched off.
Even when we change painting fat lines using a VCL-Method to paint the
non-expanded polygon as fat line, internally VCL will do the same line segment
preparations, using the exact same tooling from basegfx. The only difference
would be that the prepared geometry is not buffered in the primitive
decomposition, but preared with each paint in VCL. When there exists a VCL fat
line painting method which directly paints the fat line, we can change this and
support it.
So the key for performance now IS either VDEV preparation or PolyPolygon
painting/preparation for XRender. Both is VCL-specific.
---------------------------------------------------------------------
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: issues-unsubscr...@graphics.openoffice.org
For additional commands, e-mail: issues-h...@graphics.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org
