Re: [chlor-develop] CSegment

[<chl...@li...>]

> Fair enough, I 'll add it back.

Thanks.

> out of sync with the object. We need to decide if we will prevent  
> changing internal objects (change certain objects to immutable  
> objects) or create the boundingbox always dynamically.
> I prefer the first, a little overhead at first but when carefully  
> constructed, the easiest to work with. Creating a bounding box  
> everytime when needed, might be too

I prefer the first as well.

> A third possibility where a parent is notified everytime a child  
> object is modified, adds too much complexity and can fail very easily.

I don't see the contradiction here. If a visitor modifies a segment,  
the parental path needs to be informed. The segment can do that, like  
we currently have it. We just should prevent direct access to the  
NSMutableArrays.

Lenny