You don't believe that, do you?
I believe it is the third-best solution, if the first two I mentioned
are unavailable.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Sat, 20 Jan 2007 23:36:25 +0100, Jamie Zawinski <[EMAIL PROTECTED]> wrote:
I think you should take my word for it that this bug is *unfixable* on
the xscreensaver side. Your patch will not fix it, it will just move
the bug around. People have been complaining about this for literally
t
I think you should take my word for it that this bug is *unfixable*
on the xscreensaver side. Your patch will not fix it, it will just
move the bug around. People have been complaining about this for
literally ten years, and in all that time, nobody (including me) has
come up with a patch
tags 354559 = patch
thanks
Hello,
to clarify the issue, please look in the documentation of Xlib. You'd find
that if a client has a (keyboard or pointer) grab, the server only sends
keyboard or pointer events to this client. If xscreensaver is not using any
extensions or /proc/interrupts (which
Hello,
I think the problem is the nuke_focus thing. The problem is that
if some app has keyboard grab, you cannot determine any (keyboard)
user activity. Xscreensaver shouldn't do anything if some other
app has grab and xscreensaver is not using xxx-server extension or
/proc/interrupts. It can be
5 matches
Mail list logo
