Re: The Problems with NSController
Re: The Problems with NSController
- Subject: Re: The Problems with NSController
- From: Thomas Lachand-Robert <email@hidden>
- Date: Sun, 26 Oct 2003 19:07:55 +0100
Le dimanche, 26 oct 2003, ` 15:42 Europe/Paris, Aaron Hillegass a icrit
:
5. It relies on unsavory hacks to the runtime system. For a
controller to know about changes to a model object, your accessor
methods need to notify it of the change. In EOF, the developer added a
call to [self willChange] to each set method in his model objects.
NSController (which doesn't trust you to do this) replaces your class
with a secret subclass that does the "right" thing.
Could you (or anyone else) elaborate on this? I just don't understand
the "magic" of Key-Value Observing: is there a huge performance penalty
for that?
3. It has no support for undo. EOF automatically registered all
edits, inserts, and deletes with the undo manager.
Then, what's the recommended way to support undo with NSControllers?
Thanks,
Thomas Lachand-Robert
********************** email@hidden
<< Et le chemin est long du projet ` la chose. >> Molihre, Tartuffe.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.