On Fri, Aug 22, 2008 at 10:58 AM, Paul Bruneau <[EMAIL PROTECTED]> wrote: > I am forcing the view to update after a change to one of the order step > objects in what I am sure is The Wrong Way™ by basically chucking > setNeedsDisplay into areas of my code such as the contextual menu handling > code, etc. This works great for GUI-driven changes even though it's wrong, > but it falls apart of course when changes occur due to Applescript.
Are you saying that when some GUI event occurs (like clicking a button), you are calling -setNeedsDisplay: on your custom view? Where's is your controller object? All of your model changes should be going through a controller, and this controller would know to update the other views. --Kyle Sluder _______________________________________________ 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]
