Hi Jens, > I know it’s considered rude to answer a coding question with a UI critique, > but the best solution would really be to avoid using a modal dialog at all. > They’re a poor user experience compared to a sheet or some other kind of > in-window display, and as you’ve seen, they can cause complications with > runloops.
You're right. I will probably change this in the near future, but I really need a way to synchronously pick up an entity. > The runloop isn’t stopped, it’s just running nested in a different mode > (NSModalPanelRunloopMode). But most API methods that schedule things only > schedule them in the default runloop mode, so they won’t get time to run > while a model panel is up. The workaround is to use variant scheduling > methods that take an array of runloop modes (usually it’s an extra parameter > like “inModes:”), and explicitly let them run in the modal mode. I'll try to register my window controller as an observer for the selected property of the NSArrayController. That should do the trick: I always select a newly inserted object. _______________________________________________ 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
