Re: Warning users when editing multiple items
Re: Warning users when editing multiple items
- Subject: Re: Warning users when editing multiple items
- From: Graham Cox <email@hidden>
- Date: Thu, 07 Feb 2013 16:16:42 +1100
On 07/02/2013, at 2:19 PM, Patrick Cusack <email@hidden> wrote:
> It's sort of a misnomer as the control only applies changes to my multiple items if I type anything and tab from the control. I don't have to press return. Weird.
It's not weird.
Consider what would happen if it didn't do that. You would type a value into a field, then go to another field to enter a value there. If the first value wasn't pushed to the model, it would mean that the model is in a state different from what you see in your interface. If it's not committed then, then when? There's no other reasonable time to do it - the user might enter something then come back to it hours later, having forgotten that they have not committed earlier edits.
What you see in your interface should, to a reasonable degree, be the state of your model. During actual editing that isn't the case, but as soon as there is any action that changes focus, the commit will be made.
iTunes doesn't show the alert on commit - it shows it when Get Info is chosen for multiple items, before it even shows the panel. To me that's about as poor a way to deal with the problem as I've seen, since a) it might be much later you "commit" the changes and have forgotten it was for multiple items and b) the alert is itself optional - the user can elect not to have it show. The only escape is the fact the iTunes' Get Info dialog is app modal - you have to click OK to commit all the edits, and have the option to Cancel. These days that's a very old fashioned way to do it, but in iTunes' case it kind of makes the situation less dire than it might be, since if in doubt you can Cancel. It also has the rather strange (and as far as I know, unique to itself) additional checkbox next to each field, selecting what items you want to actually change.
For a modern live interface, you should use another approach.
--Graham
_______________________________________________
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