> On 2015 Jan 16, at 21:35, Rick Mann wrote:
>
> The problem I see with two controllers has to do with managing the selection,
> and numerous other problems. For example, I have an inspector that's looking
> at the "current selection." How does it consider the unified selection of
> both cont
> On Jan 16, 2015, at 21:20 , Jerry Krinock wrote:
>
>
>> On 2015 Jan 16, at 20:58, Rick Mann wrote:
>>
>> A "Part" in my app has a set of geometric primitives, and a set of labels
>> (both have a common base class). These are two separate sets (arrays) on the
>> part. But when editing the
> On 2015 Jan 16, at 20:58, Rick Mann wrote:
>
> A "Part" in my app has a set of geometric primitives, and a set of labels
> (both have a common base class). These are two separate sets (arrays) on the
> part. But when editing the part, they can each be clicked on and edited. I
> want to use
I'm working on a specialized CAD program with a fairly complicated model, not
using Core Data. The data is hierarchical in nature, but not homogeneously.
A "Part" in my app has a set of geometric primitives, and a set of labels (both
have a common base class). These are two separate sets (arrays
