On Tue, Feb 8, 2011 at 11:19 AM, daspostloch <[email protected]> wrote:

> I use LilyTerm and observe the following:
>
> IF Evince=Maximized, Mouse=NotOnShellWindowTitle
> THEN Evince steals focus, hops on top, keeps focus
>
> IF Evince=Maximized, Mouse=AnywhereInTitleBar
> THEN Evince hops on top and the calling shell keeps the focus
> (Note that it does not matter where in the Title bar:
>  clock, workspaces, another shell, all the same).
>
> I got a bit confused about what you want to happen,
> but my opinion is, nothing should pop up by itself,
> but if it does, it should also take the keystroke focus.

Thank Spaghetti Monster!  This is exactly what I witness and precisely
the behavior I expect (with the very same conditional: "but if it
does").

> Under this assumption we summarize: don't park the
> mouse pointer in the awesome title bar when you plan
> to modify a file that is open in a fullscreen
> instance of evince. This will avoid keystrokes
> being sent to apps you don't currently see.
> For me, that's an OK rule

I don't expect the behavior of my WM to change according to the
*position* the mouse is at.  I would flag that as a bug.

> In my opinion a bug fix for evince should fix
> evince hopping on top, and then of course the
> focus should not change either. Then the
> awesome-mouse-pointer-in-title-bar-bug would
> not occur in the first place, and all was well.

That's right.  I'm blaming Evince and pointing out an awesome
inconsistency, as this could be triggered by other apps.

> Let's close with another goodie: if evince
> is open fullscreen on one virtual desktop,
> and you touch the file from a shell on a
> second virtual desktop, then evince puts
> itself on top on its own virtual desktop,
> but the focus in that desktop stays with
> the window that last had it.

That's right, this is how I first experienced the problem, AFAIR.

> But again, that
> would be exactly the desired behavior if
> evince didn't hop on top.

True that.  Thanks again for the investigation.

--
To unsubscribe, send mail to [email protected].

Reply via email to