There is a chance in the application where only one, borderless window displayed on the secondary screen, so there are possible circumstances where displaying a window-modal panel not quite useful.
On Dec 17, 2012, at 10:50 AM, Tom Davie <tom.da...@gmail.com> wrote: > > On 17 Dec 2012, at 09:42, Tamas Nagy <tamas.lov.n...@gmail.com> wrote: > >> The user is still able to control things like fading with a MIDI/OSC >> controller - they definitely do not do that with mouse. But there are things >> which only controllable with the UI, deleting layers for example. And there >> are some circumstances - for example, loading a whole project, where the >> app's state just reseted before displaying the open panel, and the loading >> process presume everything is clear when iterating thru the load data, so it >> could would be bad if the app's "clear state" can change when an open panel >> is opened. > > Wouldn't the correct thing in this state be to create a new project window > associated with the project document, and then fire of an open sheet for that > window so that it's only modal for the window? > > Thanks > > Tom Davie _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
