Bug#612893: fluxbox: Keypresses are lost after changing workspaces

[Marko Lerota]

This bug is still present in Fluxbox 1.3.2. Is there any chance that this would
be fixed, or everyone just stat using wmctrl?

--
Marko Lerota



--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

[Paul R. Tagliamonte]

I still can't reproduce this, I'll pass this on again, though.

Thanks for using Fluxbox,
Paul

On Sun, May 13, 2012 at 11:32 AM, Marko Lerota <mle...@gmail.com> wrote:
> This bug is still present in Fluxbox 1.3.2. Is there any chance that this would
> be fixed, or everyone just stat using wmctrl?
>
> --
> Marko Lerota
>
>
>



--

:wq

[André Glüpker]

Hello devs/Paul,

On Sun, 13 May 2012 11:48:58 -0400
"Paul R. Tagliamonte" <pau...@fluxbox.org> wrote:
> I still can't reproduce this, I'll pass this on again, though.

I think I just figured out, what causes this problem.

> void BScreen::keyPressEvent(XKeyEvent &ke) {
> if (Fluxbox::instance()->keys()->doAction(ke.type, ke.state,
> ke.keycode, Keys::GLOBAL|Keys::ON_DESKTOP))
> // re-grab keyboard, so we don't pass KeyRelease to clients
> // also for catching invalid keys in the middle of keychains
> FbTk::EventManager::instance()->grabKeyboard(rootWindow().window());
> }

If you manage to release the keys (inclusive modifier) before the
workspace-switch completed, the next key(s) will get grabbed instead of
the KeyRelease-Event.

At least I can reproduce this behaviour by hitting the keys really fast
vs. wait a second before releasing them.

Cheers,
André

[André Glüpker]

> void BScreen::keyPressEvent(XKeyEvent &ke)
Sorry, forgot to mention where to find this snippet.
It's in file "src/Screen.cc" line 789.