Re: [chlor-develop] CSegment
Status: Pre-Alpha
Brought to you by:
lenny222
|
From: <chl...@li...> - 2006-03-19 20:30:17
|
> and consistent. A bounding box at node or segment level is > absolutely not needed. I cannot agree. You need segment bounding boxes for intersection tests. Have a look at CPath's containsX: Y: for example. Not to mention Segment-segment intersections finding. > In the third option, it is possible to change the content of a node > or segment through moveTo or other methods. The parent path object > listens on changes and changes its state accordingly. This > complicates things heavily as each child node or segment needs to > keep a reference to its parent. No, that's how it works currently without parent keeping, just by means of NSNotification. I am quite satifised with the current shape of things. What we should remove is exposing low level data structes like NSMutableArrays. This includes making CPoint and CSegment read/only. Bye, Lenny |