Re: selectionShouldChangeInTableView called twice
Re: selectionShouldChangeInTableView called twice
- Subject: Re: selectionShouldChangeInTableView called twice
- From: Andreas Mayer <email@hidden>
- Date: Sun, 21 Dec 2008 15:27:09 +0100
Am 21.12.2008 um 04:14 Uhr schrieb Andre Masse:
Now, suppose the user somehow move the focus from the detail view
(by switching application and coming back, accidently clicking in
the master view or whatever). This is a third case, he may have not
completed its modifications and should be able to continue editing
the record.
All these cases somehow involve user errors. If this really is a
problem, why not introduce a separate edit mode?
I.e. in browse mode all fields in the detail pane are locked as in
*not* editable. To edit anything the user has to enter edit mode (by
clicking a button, selecting a menu command etc.). This will unlock
the fields in the detail pane and *disable* the master view. That way
the user always has to end editing explicitly to change records.
Just an idea.
Andreas
_______________________________________________
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