To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=99385
------- Additional comments from [email protected] Fri Apr 24 13:48:58 +0000 2009 ------- AW: Looked at OverlayTableBorder. First thing is that he HitTest at the OverlayObject is used; this is not optimal since that test was only added test-wise and is not completely implemented in OverlayObjects. Replaced by implementing the test as TableBorderHdl::IsHdlHit() directly. Second thing is that it seems as if the hatch border was originally planned to be 6 discrete units (pixels) wide. To do this, it would have been necessary to implement zoomHasChanged() for OverlayTableBorder to react accordingly and to re-create the visualisation. This again would need a more abstract (intelligent) OverlayTableBorder object which is defined by a range and a discrete radius of 6 pixels. As it is defined now it is dangerous and leads internally to assumptions, e.g. that there are two polygons and these are rectangles, etc... I will implement a more general OverlayTableBorder for the primitive migration... --------------------------------------------------------------------- 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]
