Issue 73044 - UNO API Polygon does not support open/closed states
Summary: UNO API Polygon does not support open/closed states
Status: CONFIRMED
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All All
: P3 Trivial
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-02 12:43 UTC by Armin Le Grand
Modified: 2017-05-20 11:27 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Armin Le Grand 2007-01-02 12:43:06 UTC 
AW: Other bugs revealed: We have a problem with our UNO API Polygon definition(s).
Motivation: We have internal PolyPolygons with curve and open/close abilities
(basegfx::B2DPolyPolygon) and we have tooling support for svg:d which also
supports PolyPolygon, open/closed state and curves. But we have a set of UNO API
PolyPolygons which lack open/closed ability and thus there are round-trips over
UNO API (e.g. XLineStartItem::QueryValue() and XLineStartItem::PutValue()) which
do not preverve the closed state and thus loose information.
I will quick-fix involved bugs for now (e.g. #i72807#), but this involves some
shortcomings.

AW: For a clean solution i suggest replacing all polygon and PolyPolygon and
curve usages in API with svg:d.
We will need to thoroughly plan this but at least do it in a mid-time frame to
solve the problem.
Comment 1 Armin Le Grand 2007-06-15 14:41:11 UTC 
AW->CL: Found another serious caveat: When using C1 or C2 and saving/loading,
the C1/C2 is lost due to API using integer polygons for transport. We need to do
something here soon!
Comment 2 clippka 2007-09-12 17:08:02 UTC 
retarget
Comment 3 Marcus 2017-05-20 11:27:33 UTC 
Reset assigne to the default "issues@openoffice.apache.org".