Re: runModalForWindow() doesn't re-activate former window upon return

On 26.08.2016 at 17:24 Keary Suska wrote: >> On Aug 26, 2016, at 8:36 AM, Andreas Falkenhahn >> wrote: >> 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

Re: runModalForWindow() doesn't re-activate former window upon return

> On Aug 26, 2016, at 8:36 AM, Andreas Falkenhahn > wrote: > > 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

Re: runModalForWindow() doesn't re-activate former window upon return

On 26.08.2016 at 16:19 Keary Suska wrote: >> On Aug 25, 2016, at 12:51 PM, Andreas Falkenhahn >> 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

Re: runModalForWindow() doesn't re-activate former window upon return

On 25.08.2016 at 22:36 Kyle Sluder wrote: > -mainWindow and -keyWindow don’t return pointers to windows outside of > your application. (How could they? Other applications have their own > address spaces.) They either return pointers to windows in your app > (which might be windows owned by the

Re: runModalForWindow() doesn't re-activate former window upon return

> On Aug 25, 2016, at 12:51 PM, Andreas Falkenhahn > 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

Re: runModalForWindow() doesn't re-activate former window upon return

On Thu, Aug 25, 2016, at 01:51 PM, Andreas Falkenhahn wrote: > On 25.08.2016 at 19:47 Keary Suska wrote: > > >> On Aug 25, 2016, at 9:45 AM, Andreas Falkenhahn > >> wrote: > > >> Tested it, the window is clearly main and key, this is the debug output: > > >> CHECK:

Re: runModalForWindow() doesn't re-activate former window upon return

On 25.08.2016 at 19:47 Keary Suska wrote: >> On Aug 25, 2016, at 9:45 AM, Andreas Falkenhahn >> wrote: >> Tested it, the window is clearly main and key, this is the debug output: >> CHECK: 0x10040b4d0 0x10040b4d0 0x10040b4d0 >> i.e. [NSApp mainWindow], [NSApp

Re: runModalForWindow() doesn't re-activate former window upon return

> On Aug 25, 2016, at 9:45 AM, Andreas Falkenhahn > wrote: > > Tested it, the window is clearly main and key, this is the debug output: > > CHECK: 0x10040b4d0 0x10040b4d0 0x10040b4d0 > > i.e. [NSApp mainWindow], [NSApp keyWindow] and my NSWindow pointer are > exactly

Re: runModalForWindow() doesn't re-activate former window upon return

On 25.08.2016 at 17:21 Ken Thomases wrote: > On Aug 25, 2016, at 6:51 AM, Andreas Falkenhahn > wrote: >> Isn't runModalForWindow() supposed to activate the window which formerly >> had the focus when it returns? It doesn't do this here. When >> runModalForWindow() >>

Re: runModalForWindow() doesn't re-activate former window upon return

On Aug 25, 2016, at 6:51 AM, Andreas Falkenhahn wrote: > > Isn't runModalForWindow() supposed to activate the window which formerly > had the focus when it returns? It doesn't do this here. When > runModalForWindow() > returns, the window that was active when I called

runModalForWindow() doesn't re-activate former window upon return

Isn't runModalForWindow() supposed to activate the window which formerly had the focus when it returns? It doesn't do this here. When runModalForWindow() returns, the window that was active when I called runModalForWindow() isn't made active again. Of course, I could do this manually by calling