Re: problem with X11 toggling full screen temporarily by itself
Re: problem with X11 toggling full screen temporarily by itself
- Subject: Re: problem with X11 toggling full screen temporarily by itself
- From: raf <email@hidden>
- Date: Thu, 28 Oct 2010 12:49:56 +1100
- Mail-followup-to: email@hidden
Ambrose LI wrote:
> On 26 October 2010 14:27, robert delius royar <email@hidden> wrote:
> > Tue, 26 Oct 2010 (11:38 -0600 UTC) Bob wrote:
> > rootless, and on my old PPC the loss was enough that I dropped characters
> > while typing in an xterm. Sometimes entire words would be lost. In other
> > cases the text would go to the wrong window, which I think is caused by an
> > intersection of this bug and the one where coming out of screen sleep causes
> > the x11 windows to be on top but not with focus.
>
> Now that I have actually done the plunge and upgraded to 10.6, I have
> to say that this is a very serious problem. This is IMHO, very
> dangerous behaviour (and the general slowness of 10.6 only makes it
> worse), especially when what's taking away your focus is an error
> message, password prompt, or some other nasty thing. I hope Apple can
> look into ways to address this "focus stealing" problem (not just in X
> but the MacOS X system in general) seriously.
>
> --
> cheers,
> -ambrose
it's just as bad when what's taking away the focus is
completely invisible because you still lose keystrokes.
i think it's a tricky problem. sometimes i want it to
happen. e.g. if i type "open http://something"; in X11, i
don't mind X11 automatically toggling out of full screen
mode and focus leaving to take me to the browser that i just
launched (but i'd be just as happy to navigate my way to the
browser window myself if X11 could forcibly retain focus
until i tell it to let go).
the fault probably lies with all the programs that we think
should be running in the background acting instead like
foreground user interface programs.
programs like GoogleSoftwareUpdateAgent apparently can
sometimes open a window (although i'd never seen that
happen) and so just because it might open a window it
behaves as though it is going to open a window but then
decides not too.
similarly with iCal, it's checking to see if there is an
appointment to tell you about. if there is one, it will need
to pop up a window or something to tell you but if there
isn't it's too late not to take focus. i'm guessing a bit
about iCal, though.
it would be nice if these were reimplemented as two
processes; one that doesn't take focus and decides whether
or not it needs to open a window and, if so, launches a
separate process that does so (or a single process that
doesn't initialise the user interface related libraries
until it is known that they are needed). i can't really see
anyone doing anything about this to all the programs that
would need to be "fixed".
apple probably could suggest in the launchd documentation
that writers of launchd agents don't take focus without good
reason ("man launchd.plist" already lists expectations of
what launchd agents/daemons should and shouldn't do) but
it's probably too late for that now.
however, i would have thought that there must be a fairly
large number of users using both iCal and FrontRow (or any
other popular full screen media viewing application) and
this would be a problem there as well but perhaps it isn't.
i'm just delighted that yesterday was completely
flicker-free for me and that if the flickering starts again,
i know how to track down the culprit (see "man praudit" and
"man audit_user"). i just hope i never run into the
situation where i need the culprit as much as i need X11 but
i think that that's unlikely for me.
cheers,
raf
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden