FROM : Stefan
DATE : Sun Aug 13 22:47:21 2006
Am 13.08.2006 um 18:24 schrieb Kaelin Colclasure:
> On Aug 13, 2006, at 4:58 AM, Stefan wrote:
>
>> Using option-dragging an entity to a window, IB creates a default
>> editor
>> with respective controllers - each time new controllers, even if
>> the entity
>> has already NSArrayControllers in the nib.
>>
>> Although I think this isn't a real problem, I don't like it.
>>
>> Does anybody know, if I can consolidate to identical controllers to
>> one without breaking bindings?
>
> If you're asking if you can manually re-bind all of the view
> bindings to use one controller, then yes, that will work fine. I
> don't know of any way to "consolidate" the bindings short of doing
> it manually, one-at-a-time, though.
>
>> Moreover, I'd like to know, why IB creates identical controllers.
>> Aren't
>> identical controllers bad style?
>
> Not necessarily. You may want more than one controller for an
> entity if, for example, you want to use different filter predicates
> in different views. IB has no idea what you might get up to, so it
> creates the most conservative case -- a different controller for
> each view.
Thx! This is very reasonable. Alone: If I'd like to clean up stuff, it
is an enormous amount of work. Basically, all bindings get lost.
DATE : Sun Aug 13 22:47:21 2006
Am 13.08.2006 um 18:24 schrieb Kaelin Colclasure:
> On Aug 13, 2006, at 4:58 AM, Stefan wrote:
>
>> Using option-dragging an entity to a window, IB creates a default
>> editor
>> with respective controllers - each time new controllers, even if
>> the entity
>> has already NSArrayControllers in the nib.
>>
>> Although I think this isn't a real problem, I don't like it.
>>
>> Does anybody know, if I can consolidate to identical controllers to
>> one without breaking bindings?
>
> If you're asking if you can manually re-bind all of the view
> bindings to use one controller, then yes, that will work fine. I
> don't know of any way to "consolidate" the bindings short of doing
> it manually, one-at-a-time, though.
>
>> Moreover, I'd like to know, why IB creates identical controllers.
>> Aren't
>> identical controllers bad style?
>
> Not necessarily. You may want more than one controller for an
> entity if, for example, you want to use different filter predicates
> in different views. IB has no idea what you might get up to, so it
> creates the most conservative case -- a different controller for
> each view.
Thx! This is very reasonable. Alone: If I'd like to clean up stuff, it
is an enormous amount of work. Basically, all bindings get lost.
| Related mails | Author | Date |
|---|---|---|
| Stefan | Aug 13, 13:58 | |
| Kaelin Colclasure | Aug 13, 18:24 | |
| Stefan | Aug 13, 22:47 |






Cocoa mail archive

