[graphics-issues] [Issue 112245] Assertion: Polygon::Poly gon: Too many points in given B2DPolygon, need to reduce hard to
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=112245 User wg changed the following: What|Old value |New value Status|RESOLVED |VERIFIED --- Additional comments from w...@openoffice.org Wed Jun 30 10:27:04 + 2010 --- Verified in CWS. - 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
[graphics-issues] [Issue 112245] Assertion: Polygon::Poly gon: Too many points in given B2DPolygon, need to reduce hard to
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=112245 --- Additional comments from a...@openoffice.org Tue Jun 29 11:08:32 + 2010 --- AW: Re-checked with wntmsci12.pro build. Works as expected. - 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
[graphics-issues] [Issue 112245] Assertion: Polygon::Poly gon: Too many points in given B2DPolygon, need to reduce hard to
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=112245 User aw changed the following: What|Old value |New value Assigned to|aw|wg --- Additional comments from a...@openoffice.org Tue Jun 29 11:16:01 + 2010 --- AW-WG: Please review. - 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
[graphics-issues] [Issue 112245] Assertion: Polygon::Poly gon: Too many points in given B2DPolygon, need to reduce hard to
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=112245 User aw changed the following: What|Old value |New value Target milestone|OOo 3.x |OOo 3.3 --- Additional comments from a...@openoffice.org Thu Jun 24 10:49:46 + 2010 --- AW: Adapted target - 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
[graphics-issues] [Issue 112245] Assertion: Polygon::Poly gon: Too many points in given B2DPolygon, need to reduce hard to
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=112245 --- Additional comments from i...@openoffice.org Mon Jun 21 08:51:02 + 2010 --- The difference with the old chart was that it didn't use the UNO API and had no ways of reducing point count. The new chart has already mechanisms to reduce the point count. There are only a few cases left, where this is not effective, for example if signals are very noisy or as it seems with splines - issue 1120072. - 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
[graphics-issues] [Issue 112245] Assertion: Polygon::Poly gon: Too many points in given B2DPolygon, need to reduce hard to
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=112245 --- Additional comments from i...@openoffice.org Mon Jun 21 08:53:06 + 2010 --- typo: meant issue 112072 - 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
[graphics-issues] [Issue 112245] Assertion: Polygon::Poly gon: Too many points in given B2DPolygon, need to reduce hard to
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=112245 --- Additional comments from a...@openoffice.org Fri Jun 18 16:42:19 + 2010 --- AW: Line splitting woks well now. AW: For filled polygon handling i need to take care of five palces: PolyPolygonBitmapPrimitive2D, PolyPolygonHatchPrimitive2D, PolyPolygonGradientPrimitive2D and PolyPolygonColorPrimitive2D. Also need to care in PolyPolygonColorPrimitive2D in the direct handling of PolyPolygonColorPrimitive2D. Added code which can be used recursively to split the fill polygon into right/left resp. top/bottom pairs by clipping. Tested with 30 points maximum (due to curves needing already 3 points per edge). Added code foer curve handling. All cases except the first correct the polygon and directly create Metafile actions and/or call VCL with that polygon. Only the first case needs to call the rendere itself recursivey. AW: PS: Met BM by coincidence yesterday; he told me that he remembers that exactly this problem was araedy fixed in the old chart module, also splitting the geometry. I think this is the right place and shold also be changed there;it's simply also a question of cost when such hge polygons get created. Nonetheless, it has to work in Metafie stuff (which is VCL, not Drawinglayer). AW: Re-checking plane splitting... - 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
[graphics-issues] [Issue 112245] Assertion: Polygon::Poly gon: Too many points in given B2DPolygon, need to reduce hard to
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=112245 User aw changed the following: What|Old value |New value Status|STARTED |RESOLVED Resolution| |FIXED --- Additional comments from a...@openoffice.org Fri Jun 18 17:14:58 + 2010 --- AW: Okay, works well. Checked in, 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...@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
[graphics-issues] [Issue 112245] Assertion: Polygon::Poly gon: Too many points in given B2DPolygon, need to reduce hard to
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=112245 --- Additional comments from a...@openoffice.org Thu Jun 17 12:09:49 + 2010 --- AW: Nees to be done for SvtGraphicStroke and SvtGraphicFill. For SvtGraphicStroke it's in PolygonHairlinePrimitive2D, PolygonStrokePrimitive2D and in PolygonStrokeArrowPrimitive2D. Adding code, checking... - 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
[graphics-issues] [Issue 112245] Assertion: Polygon::Poly gon: Too many points in given B2DPolygon, need to reduce hard to
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=112245 --- Additional comments from a...@openoffice.org Thu Jun 17 15:06:38 + 2010 --- AW: To test, i limited possible points per polygon to 10. Added code to line splitting to take open/closed into account. Added code to take curves into account. Works as expected. Needs to be called recursively; done by creating new primitives and -re-spawning metafile primitive processor with those. AW: Let's split fille dpolygons now... - 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
[graphics-issues] [Issue 112245] Assertion: Polygon::Poly gon: Too many points in given B2DPolygon, need to reduce hard to
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=112245 --- Additional comments from a...@openoffice.org Thu Jun 17 15:11:33 + 2010 --- AW: Oops, some changes in VclMetafileProcessor2D will collide with CWS aw082. HG allows to get aw082 into aw083, doing that... AW: Went well, no conflicts. On we go... - 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
[graphics-issues] [Issue 112245] Assertion: Polygon::Poly gon: Too many points in given B2DPolygon, need to reduce hard to
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=112245 User aw changed the following: What|Old value |New value Status|NEW |STARTED --- Additional comments from a...@openoffice.org Wed Jun 16 15:15:11 + 2010 --- AW: Again looked into expanding the tools Polygon to 32bit point count. The basic change is not too hard (except looking at all places working with a polygon), but the problem is in the stream and Read/Write operators. There, a wild mixture of ImplWrite/Write and the stream operators are used. Only Write(...) uses a version info and could possibly be 'persuaded' to write polygons with more than 65535 points possibly. Many usages (esp. the Metafile actions) use the stream operator or even ImpWrite. There are even places where usages stream the points directly (using NO method for Polygon at all). All this comes from a endless story of changes/fixes around the tools Polygon and it's expansions; e.g. the stream operators do not even stream the control point flags (!) All in all: too dangerous to do. It's better to not touch the Metafile and it's polygon usages, if avoidable. But how to avoid? I thought about strategies of point reduction (clipping, weighted point relevance), but that will lose resolution. The only way to reduce this problem is to do it where it happens: At the Metafile creation. In this concrete case, it's a line polygon which could simply be splitted into many shorter ones. This is also the way to stay backward compatible. Thus, for lines, split them in halfs. For filled polygons, clip them hor/vertically when too complex. Looking where this could be done best... - 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
[graphics-issues] [Issue 112245] Assertion: Polygon::Poly gon: Too many points in given B2DPolygon, need to reduce hard to
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=112245 Issue #|112245 Summary|Assertion: Polygon::Polygon: Too many points in given | B2DPolygon, need to reduce hard to Component|Drawing Version|DEV300m80 Platform|All URL| OS/Version|All Status|NEW Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|code Assigned to|aw Reported by|iha --- Additional comments from i...@openoffice.org Wed Jun 9 10:41:31 + 2010 --- Load the example doc BigSmoothPoly.xls from issue 112072 with dev300m80 non pro. - There are popping up assertions Polygon::Polygon: Too many points in given B2DPolygon, need to reduce hard to maximum of tools Polygon (!). The result is an incomplete painted chart. @aw, please have a look at the rendering code. It seems that the number of points that can be set via API and the number of points that can be processed in reality do not match. I keep issue 112072 to work on possible reduction of points on chart side for this special case. But the problem in the general rendering code should be fixed also. - 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
[graphics-issues] [Issue 112245] Assertion: Polygon::Poly gon: Too many points in given B2DPolygon, need to reduce hard to
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=112245 --- Additional comments from a...@openoffice.org Wed Jun 9 12:00:10 + 2010 --- AW: It's the old tools Polygon which is defined to have UINT16 nPoints. That's one of the reasons to have basegfx and the new polygons created, besides numerical problems (integer vs. double precision). Problem is that this old tools Polygon is so centrally used throughout the existing codebase that changing it to 32bit PointCount will certainly make hell break lose. It comes into play with charts e.g. due to Metafile usage. The tools Polygon is streamed into and read from file-based Metafiles; this means these need to be adapted, thus backward compatibility will break, too. Also unknown things (just examples which come to my mind, there will be more): Does WMF support more than 16Bit point count (if no, we can no longer export to clipboard). Could all places be found which are based on Tools Polygon's Point Count? If yes, how many will this be and could they all be adapted at all? Will VCL be adaptable to it and (more important) are all our systems able to render such big polygons at all? At least not HW-supported; rendering HW (graphiccards) have a limited amout of line span entries, so rendering will anyways fallback to soft renderers (usually with more than 4096 or 8192 points or similar). All in all: A known problem already worked around (as can be seen: the whole current DrawingLayer visualisation does not use the tools polygon anymore), dangerous to touch. The preferred fix would definitely be to reduce point count. How can a smoothing of a polygon with ca. 4000 points lead to one with 79959 points...? Also to think about: Is it a defect, or (as it always was this way) is it an enhancement...? - 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
[graphics-issues] [Issue 112245] Assertion: Polygon::Poly gon: Too many points in given B2DPolygon, need to reduce hard to
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=112245 --- Additional comments from i...@openoffice.org Wed Jun 9 12:35:09 + 2010 --- The resolution for the spline calculation is set to 20, that causes the immense grow of point count. The reduction of point count on chart side will be addressed with separate issue 112072. So this one should concentrate on the rendering engine. I think it is definitely a defect if API and implementation do not match in dimensioning. In long term this should be solved. In short term I can live with workarounding. - 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
[graphics-issues] [Issue 112245] Assertion: Polygon::Poly gon: Too many points in given B2DPolygon, need to reduce hard to
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=112245 --- Additional comments from a...@openoffice.org Wed Jun 9 12:55:49 + 2010 --- AW: This one will concentrate on finding a solution on rendering side, of course. There are already the basics (new basegfx stuff), but the old office (and definitions of the forefathers) is in the way (as often) :-( The long run plan is anyways to get rid of the tools polygon completely. It is a defect in the sense of the API, when the whole office (unfortunately containing many old parts) is seen as implementation. It's an enhancement when knowing that the office comes from never having been able to do such polygons and gets better step by step. At least it should not lead to define the UNO API as accepting only polygons with 65536 points, else throwing exceptions (which would have been a must when defining the API at the time it was defined :-)). - 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
[graphics-issues] [Issue 112245] Assertion: Polygon::Poly gon: Too many points in given B2DPolygon, need to reduce hard to
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=112245 --- Additional comments from a...@openoffice.org Wed Jun 9 13:03:31 + 2010 --- AW: Just tried: Activating the 2nd chart (the smoothed one) shows that Drawinglayer is perfectly capable of handling these polygons; so is printing and PDF exporting (using the ChartPrettyPainter). It's just the transport over the old Metafile and it's tools Polygons... - 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
[graphics-issues] [Issue 112245] Assertion: Polygon::Poly gon: Too many points in given B2DPolygon, need to reduce hard to
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=112245 --- Additional comments from a...@openoffice.org Wed Jun 9 13:24:16 + 2010 --- AW: The idea of expanding the tools polygon in the Metafile has just died; there is a VersionCompat written and read when writing the polygon (Polygon::Write and Polygon::Read), but it is not computed at read time. Thus, all offices out there are not able to read the polygon in it's evtl. offered old form and could not read updated Metafiles. ARGH. - 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
