On 26.08.2016 at 16:19 Keary Suska wrote:
>> On Aug 25, 2016, at 12:51 PM, Andreas Falkenhahn <andr...@falkenhahn.com> >> wrote: >>> What happens if you add -orderOut: to the button action method? >> Ok, this solves the problem. But still, shouldn't this be handled >> automatically >> by runModalForWindow()? Why does it activate a window that doesn't belong to >> my application when it returns? That doesn't look reasonable to me at all... > Apparently not: > https://developer.apple.com/library/mac/documentation/Cocoa/Conceptual/Sheets/Tasks/UsingAppModalDialogs.html Thanks, that's what I was looking for. I just wish such essential information wouldn't be hidden in the accompanying documentation. This should really be mentioned in the documentation of runModalForWindow() or stopModal()/stopModalWithCode() IMHO. Here it is again: "It is important to call orderOut: when finished with your dialog, or it is not removed from the screen." -- Best regards, Andreas Falkenhahn mailto:andr...@falkenhahn.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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
