Apache OpenOffice (AOO) Bugzilla – Issue 78150
geometry::RealBezierSegment2D needs API change
Last modified: 2017-05-20 11:27:49 UTC
AW: geometry::RealBezierSegment2D uses (P, C1, C2)-style bezier definition. This is bad for several reasons: - C1 == P and C2 == P is used to express C1 resp. C2 are unused. This is true for C1, but for C2 it would need to be expressed with the next P in the next data section. Because usage of C2==P, a C2 which points (is equal) exactly from next P to P is not expressable. - using (Prev, P, Next)-style definition allows that - it also allows to compute/change continuity with a single segment - it also allows handling a point and it's controls with a single index AW->THB: As we discussed, we should change this to a definition which does not prevent data combinations. For the listed reasons, i propose (Prev, P, Next)-style.
Set proper target
While doing so, also get rid of the tools polygon conversion in vcl::unotools (hard to maintain, with the changed semantics); and review the places in cppcanvas, where several back-and-forth conversions between tools polygon and basegfx polygon take place (e.g. in polypolygonaction.cxx)
Sorry, out of time for 2.4
Retargetting due to resource constraints
Reset to default bug assignee.
ALG: Taking ownership
Reset assigne to the default "issues@openoffice.apache.org".