Re: dismissing one sheet for another problem
Re: dismissing one sheet for another problem
- Subject: Re: dismissing one sheet for another problem
- From: "M. Uli Kusterer" <email@hidden>
- Date: Tue, 18 Jan 2005 18:32:14 +0100
At 10:39 Uhr -0600 18.01.2005, Dan Saul wrote:
It states that you are not suppoed to do that in HIG, however it is
supported and it does work, hell even XCode does this (can't remember
where off the top of my head however).
It is *definitely* bad UI design to have a series of (nested or
sequential) dialogs or sheets. However, I've long given up on trying
to pound sense into people hell-bent towards producing bad GUI. If
they do bad UI, I can do an app that does the same as theirs and
steal their market. So why would I want to stop them? :-p
Seriously, in the case of an error dialog I'd tolerate a second sheet
after a sheet. In typical use, error dialogs shouldn't happen (if
they do, you should rethink your design to include better, and
different feedback). So, typically it's just one sheet and that's it.
If something goes wrong once that sheet has been okayed, the user
won't be confused by that second sheet folding out.
If you have more than these two, though, or it's not an error but
rather the expected behavior to have the second sheet, your design is
wrong. You should either show the results in the second sheet, or not
be using a sheet at all, but rather a separate window.
As a general rule of thumb, if your sheet contains more than a choice
of buttons or a choice of items from one list, it's very likely that
you'd do your users a favor by changing the sheet to be a regular
window instead.
--
Cheers,
M. Uli Kusterer
------------------------------------------------------------
"The Witnesses of TeachText are everywhere..."
http://www.zathras.de
_______________________________________________
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