![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
... or why my job is necessary:
Upon construction of a MultiCurve where the constructor takes a Curve or which may contain multiple CurveSegments per Curve (MultiCurve and MultiCurve), the actual Curves contained in the constructed MultiCurve are altered to always contain only one CurveSegment per Curve. Currently, the only types of CurveSegments that exist are LineStrings.
Curves containing multiple LineString CurveSegments have the LineStrings combined to form one large LineString.
(from someone on a help authoring list).
Upon construction of a MultiCurve where the constructor takes a Curve or which may contain multiple CurveSegments per Curve (MultiCurve and MultiCurve), the actual Curves contained in the constructed MultiCurve are altered to always contain only one CurveSegment per Curve. Currently, the only types of CurveSegments that exist are LineStrings.
Curves containing multiple LineString CurveSegments have the LineStrings combined to form one large LineString.
(from someone on a help authoring list).
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
no subject
Date: 2004-11-12 11:02 am (UTC)From:no subject
Date: 2004-11-12 11:18 am (UTC)From:no subject
Date: 2004-11-12 11:21 am (UTC)From:As the (remarkably old) advert says, 'Speak English, boy!'
no subject
Date: 2004-11-12 12:32 pm (UTC)From:Makes me wonder, though - if multicurves contain only single-curvesegment curves, and curves can contain more than one curvesegment, what's the difference between a multicurve with several single-curvesegment curves and a curve with multiple segements? Madness.
Now, if curves could contain both curves and curvesegments, you can build a complex curve as a recursive structure, and you can get rid of multicurves altogether. Which would make everything simple.
no subject
Date: 2004-11-12 02:24 pm (UTC)From:no subject
Date: 2004-11-12 02:25 pm (UTC)From: