Re: runModalForWindow() doesn't re-activate former window upon return
Re: runModalForWindow() doesn't re-activate former window upon return
- Subject: Re: runModalForWindow() doesn't re-activate former window upon return
- From: Andreas Falkenhahn <email@hidden>
- Date: Fri, 26 Aug 2016 16:36:53 +0200
On 26.08.2016 at 16:19 Keary Suska wrote:
>> On Aug 25, 2016, at 12:51 PM, Andreas Falkenhahn <email@hidden> 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:email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden