Hi,

I have a problem using Evince with Awesome: when changing tags, often -- but
not always -- Evince seems to miss the "focus in" event and won't recognise
any key presses until i either

    + click the window with the mouse, switch to another window and switch
    back, or

    + place the mouse over the window and execute the lua code 

        client.focus = client.focus .

I'm not sure whether this is an Awesome issue, an Evince issue, or a GTK3
issue, but i'm starting to think it's a problem with Awesome, given how the
efficacy of "client.focus = client.focus" depends on the position of the mouse
(and i can trick this "solution" a bit more by being fast enough :) ...).

I've been playing with Evince all afternoon, and have observed the following
behaviour.  When changing away from the tag with Evince in, Evince gets GTK 
events telling it that focus has changed, visibility has changed, and the
mouse has moved out of the window (if it was in the window to start with).
When changing back it reliably gets the expected visibility and mouse events,
but every so often the focus in event goes missing.

I tried to track this a little more and added a "focus" signal to see what
Awesome thinks is gaining focus.  Even in the cases when focus in goes
missing, a "focus" signal gets generated.  However, this is a bit weird,
because putting the mouse over Evince and executing client.focus =
client.focus doesn't generate a "focus" signal, but does generate the focus in
event...

A hack i did try is changing my tag switching key bindings, so it runs
awful.tag.viewprev/next then afterwards client.focus = client.focus.  This
generally stops the focus in event going missing, but i can break it by
changing tags as fast as possible -- which may point to some concurrency issue
in Awesome, if such a thing is possible (Evince is fullscreened, so it
shouldn't be the mouse thing, i think...).

So i'm at the end of my expertise :)  Any help would be appreciated...

Thanks,

Matt



-- 
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.

Reply via email to