• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: wait for sheet result
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: wait for sheet result


  • Subject: Re: wait for sheet result
  • From: Graham Cox <email@hidden>
  • Date: Fri, 8 Jan 2010 17:23:06 +1100

On 08/01/2010, at 4:24 PM, Jerry Krinock wrote:

> The Sheet Programming Guide notes that Cocoa does not support nested (or "piled on top of one another") sheets, and states that your app should make sure this never happens, but doesn't give you any assistance in doing so.  Given that sheets frequently present errors or other unexpected results, we really need a means for queueing multiple sheets, in the **unlikely** event that one's app should ever need to present two sheets to the user in rapid succession.  Hey, I know it's not pretty, but one should design to handle the corner cases.


While the guide does say this:

"Cocoa does not support the notion of cascading, or nested sheets. Per Apple Human Interface Guidelines, “when the user responds to a sheet, and another sheet for that document opens, the first sheet must close before the second one opens.”

In fact nested sheets do work fine - if you make a sheet the parent of a second sheet, it will work OK. What doesn't work is if you try and attach more than one sheet to the same parent.

I'm not saying that cascaded sheets is good UI, but if there is no option, there doesn't seem to be anything to stop you. I note that some apps, such as MS Powerpoint on Mac, go to enormous trouble to prevent more than one sheet coming up at a time, even though the app design uses several levels of cascaded dialogs. The result is shockingly bad usability, with sheets opening and closing all over the place and never really leaving you with any sense of how deep in the sequence you've gone (as you back out of the sequence, all the sheets that were called on the way pop back into view one by one). Using cascaded sheets would at least let you know you're six levels down, or whatever. Of course, cascading dialogs at all should be avoided as much as possible.

--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

  • Follow-Ups:
    • Re: wait for sheet result
      • From: Jerry Krinock <email@hidden>
References: 
 >wait for sheet result (From: Rainer Standke <email@hidden>)
 >Re: wait for sheet result (From: Graham Cox <email@hidden>)
 >Re: wait for sheet result (From: Rainer Standke <email@hidden>)
 >Re: wait for sheet result (From: Jerry Krinock <email@hidden>)

  • Prev by Date: Re: CGImageCreate performance
  • Next by Date: [iPhone] Convert date string to a NSDate object
  • Previous by thread: Re: wait for sheet result
  • Next by thread: Re: wait for sheet result
  • Index(es):
    • Date
    • Thread