On 12 Jun 2010, at 11:45, vincent wrote: > Le 12 juin 2010 à 12:28, jonat...@mugginsoft.com a écrit : > >> Modal windows fulfil a very specific purpose and manipulate the runloop >> accordingly. > > It seems some events are postponed (like timer or notifications) and some are > not affected (the object, despite the postponed creation, is nevertheless > created). > >> Are you certain that you require application modality for this functionality? > > This dialog is shown at the start of the application (before the main window > appears), that cannot be run unless the data asked for is somehow given. So > the applicationController brings up that dialog, and waits until it returns > to set up the whole context and display the main window. > > But maybe there is a way, as you suggest, to set up a different course. > It's easy then.
Make the app controller load your configuration window at launch as a normal window. When it closes you show the app window. An alternative would be to show the app window with the configuration displayed as a sheet over it. Regards Jonathan Mitchell Developer Mugginsoft LLP http://www.mugginsoft.com _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
