Re: Nested sheets
Re: Nested sheets
- Subject: Re: Nested sheets
- From: Edward Hillenbrand <email@hidden>
- Date: Thu, 31 Mar 2005 16:15:04 -0700
On Mar 30, 2005, at 4:32 PM, Bill Cheeseman wrote:
The only qualm I have about it is that an accessory view does not
focus the
user's attention the way a modal secondary sheet does. I suspect many
users
will blithely click the default button without noticing the accessory
view.
The optimal solution would be to disable the open sheets default
button. I thought this would be easy because I naively assumed the
open/save panel had accessors for the buttons. It doesn't, but its
instance variable are not declared private nor does it have a comment
stating the instance variables are private like I have seen elsewhere.
Does that mean we can use them?
An unintended choice in my utility can destroy information (although
undo/redo are available). In fact, I have decided that it is correct
to use
a critical alert sheet here, for that reason.
You could put the critical alert icon in the accessory view too.
Would this factor lead you to conclude that a modal secondary sheet is
appropriate?
I have seen it done and my first reaction was to think that something
was wrong, like the developer forgot to end the first sheet. Granted
the application in question was using two custom sheets and not the
standard open sheet and alert sheet. I just created an example app
that displays an alert sheet nested on top of on open sheet and it's
not bad. I think it can be an acceptable solution.
However, I still like my solution because it eliminates the required
extra clicks that would be introduced with a alert sheet. In the case
of a conflict with the alert sheet, the user would have to click the
default button and then click another button either to continue with
the import or to go back and select another file.
Guy and Daniel's ideas are pretty good too. A checkbox that is always
in the accessory view will definitely make the user aware that data
loss can occur, but still requires an extra click. Also, if you made
this a preference the user could forget about it and import something
that would cause data loss.
With my solution the user is never interrupted from their task. If
there is a conflict and they wish to select another file all they have
to do is select another file. If they want to import the file anyway
all they have to do is click the Import Anyway button in the accessory
view. And should they want to cancel everything, the cancel button is
there as well.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden