FROM : Nicholas Riley
DATE : Sat Jan 25 05:47:35 2003
On Fri, Jan 24, 2003 at 05:42:38PM -0700, Alex Rice wrote:
> The Cocoa docs say the correct way to handle "cascading" sheets is to
> present them one at a time, closing each one before opening the next.
> I'm in a situation where that would be a kind of a pain in the butt to
> implement. So I'm breaking that rule and just throwing up a bunch of
> sheets with NSBeginAlertSheet(). I'm catching notifications in my NSApp
> delegate, which queries my NSDocumentController, decides what document
> and window the notification belongs to, and sends the sheet to that
> window. One sheet per notification.
>
> I've noticed that for Document windows that get more than one sheet,
> only sometimes I see the behaviour where the Window dissapears after
> the last sheet is dismissed, or I can't quit out of the app, or the
> Document window is empty and white. I have a didEndSelector, but it's
> not doing anything. So is "cascading" sheets like this just an HIG
> issue or is there something worse going on here?
Yes, this is broken. Cocoa should really just prohibit it instead of
exhibiting flaky behavior.
--
=Nicholas Riley <<email_removed>> | <http://www.uiuc.edu/ph/www/njriley>
Pablo Research Group, Department of Computer Science and
Medical Scholars Program, University of Illinois at Urbana-Champaign
_______________________________________________
cocoa-dev mailing list | <email_removed>
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
DATE : Sat Jan 25 05:47:35 2003
On Fri, Jan 24, 2003 at 05:42:38PM -0700, Alex Rice wrote:
> The Cocoa docs say the correct way to handle "cascading" sheets is to
> present them one at a time, closing each one before opening the next.
> I'm in a situation where that would be a kind of a pain in the butt to
> implement. So I'm breaking that rule and just throwing up a bunch of
> sheets with NSBeginAlertSheet(). I'm catching notifications in my NSApp
> delegate, which queries my NSDocumentController, decides what document
> and window the notification belongs to, and sends the sheet to that
> window. One sheet per notification.
>
> I've noticed that for Document windows that get more than one sheet,
> only sometimes I see the behaviour where the Window dissapears after
> the last sheet is dismissed, or I can't quit out of the app, or the
> Document window is empty and white. I have a didEndSelector, but it's
> not doing anything. So is "cascading" sheets like this just an HIG
> issue or is there something worse going on here?
Yes, this is broken. Cocoa should really just prohibit it instead of
exhibiting flaky behavior.
--
=Nicholas Riley <<email_removed>> | <http://www.uiuc.edu/ph/www/njriley>
Pablo Research Group, Department of Computer Science and
Medical Scholars Program, University of Illinois at Urbana-Champaign
_______________________________________________
cocoa-dev mailing list | <email_removed>
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
| Related mails | Author | Date |
|---|---|---|
| Alex Rice | Jan 25, 01:42 | |
| m | Jan 25, 05:18 | |
| Nicholas Riley | Jan 25, 05:47 | |
| Andreas Mayer | Jan 25, 17:50 | |
| Manfred Schubert | Jan 25, 19:22 | |
| Andreas Mayer | Jan 26, 00:06 | |
| Alex Rice | Jan 26, 01:54 | |
| Jonathan Hendry | Jan 26, 07:40 | |
| Alex Rice | Jan 26, 09:41 | |
| Andy Lee | Jan 26, 18:43 | |
| Jonathan Hendry | Jan 27, 01:35 |






Cocoa mail archive

