Re: How do people typically implement dialog controllers?
Re: How do people typically implement dialog controllers?
- Subject: Re: How do people typically implement dialog controllers?
- From: Seth Willits <email@hidden>
- Date: Wed, 10 Sep 2008 22:25:29 -0700
On Sep 10, 2008, at 9:44 PM, Graham Cox wrote:
I use individual properties wherever possible. In some cases it's
appropriate to have a single dictionary to contain the settings,
because that dictionary gets passed around to other model objects
as well. But if you're model objects uses distinct properties, why
go through the trouble of having to pack them into a dictionary,
pass it to the controller, then unpack the from the dictionary from
the controller later on? It's easier to just to set and grab them
individually.
So how do you Cancel a large number of setting changes that you've
made?
I don't think I understand your question, because I don't see how
Cancel is related. If the user cancels the dialog, the callback from
the dialog/controller to the calling controller, yields the return
code. If the return code wasn't OK/Default then you don't read take on
the settings from the dialog.
--
Seth Willits
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden