On Aug 15, 2008, at 11:39 AM, Markus Spoettl wrote:
On Aug 15, 2008, at 10:23 AM, Adam R. Maxwell wrote:Sending empty willChange/didChange messages is not a good idea:http://www.cocoabuilder.com/archive/message/cocoa/2008/5/18/207038That thread gives absolutely no explanation as to why this would be harmful. Care to elaborate if you know why?
Well, I can give - at least part of - that explanation myself now. The problem with forcing notifications with willChange/didChange is that those can interfere with undo.
In my setup a central objects listens to all dependent objects' properties that can possibly be changed and registers undo operations with the undo manager as those changes happen. Using willChange/ didChange to cause a refresh of displayed values way makes the whole thing a mess.
I guess the best solution (from a design perspective) is Ron's suggestion to use proxy properties in all places where I have to use text fields to display properties that can show different values based on a preference.
Thanks for all the input! Markus -- __________________________________________ Markus Spoettl
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
