Re: focus loss issue
Re: focus loss issue
- Subject: Re: focus loss issue
- From: Brandon Allbery <email@hidden>
- Date: Sun, 23 Dec 2012 10:07:23 -0500
On Sun, Dec 23, 2012 at 5:16 AM, Lars-Johan Liman
<email@hidden> wrote:
I was thinking that maybe it's related to some common application
library that is "automagically linked in" when you build Aqua
applications of certain kinds - a subrouting you call with "the standard
template arguments" which forces a focus shift, wheras when called with
I was thinking more that when a program connects to the foreground --- whether it's doing so for interaction, or because it *might* need to interact (say, because it found an update, or the Time Machine agent finds that it's been too long since the last backup), or for some other thing that requires access to state that is normally only available via the GUI --- which might indicate a design bug at the level of OS X) --- it receives focus automatically. It then tells the GUI that it's not interested in focus or GUI events, so any events get queued and sent on to the original foreground application... but this happens too late for X11, which hooks in at a lower level than most applications. That is, it's most likely that there is no connect-for-background, just connect and then not register an interest in GUI events. And the case where it might need to register an interest in GUI events later prevents use of a hypothetical connect-without-interaction call.
This can't happen in X11 because events and focus are tied to windows and won't occur until the window is mapped, so you can just not map a window for interaction until it's needed.
That said, I know a fair amount about how event flow works in X11 but much less about how it works in Aqua.
--
brandon s allbery kf8nh sine nomine associates
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden