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


User aw changed the following:

                What    |Old value                 |New value
================================================================================
                  Status|STARTED                   |RESOLVED
--------------------------------------------------------------------------------
              Resolution|                          |FIXED
--------------------------------------------------------------------------------




------- Additional comments from a...@openoffice.org Wed Jun 24 12:23:15 +0000 
2009 -------
AW: It's used in SwContourCache::ContourRect to create a TextRanger; not sure
what this is doing, but it seems not necessary for the loaded document. It could
be done on demand. Surely TextRanger and interacting with B2DPolyPolygons may be
also optimized.
Checked: TextRanger is in SVX and internally uses PolyPolygon (the old polygon).
Checking the conversion...
Ah, here is the problem. TextRanger::TextRanger converts the B2DPolyPolygon to a
PolyPolygon, inserting all sub-polygons. The possible sub-polygon count in the
old PolyPolygon is a USHORT, allowing 65535 sub-polygons. This is a potential
problem, writing a FUp-task (#i103068#).
For OOo 3.1.1, the problem is solved with the changes done.

---------------------------------------------------------------------
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...@sw.openoffice.org
For additional commands, e-mail: issues-h...@sw.openoffice.org


---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org

Reply via email to