Keyboard navigation is buggy

[gi1242]

Sometimes the up/down keys don't work when choosing windows.

In some situations the key strokes are passed to one of the clients, and skippy takes 100% CPU.

I usually find this happens usually after navigating around a little with the keyboard, and returning to the same window. Especially if there are an uneven number of windows on each row (e.g. three windows total, two on one row, and one on the other and you use up/down.)

I can't 100% reproduce it though. (I'm using the latest version from git as of 2013-06-02, and fvwm is my window manager.)

[richardgv]

Thanks for your report! Presently skippy-xd grabs keyboard to intercept all key strokes when the main window is mapped, so really the client windows shouldn't get any keystrokes when skippy-xd is running, unless another client is grabbing the keyboard (clients with an active popup menu, for example, typically grabs the keyboard). No idea why that would happen. I have no luck reproducing the issue, either.

Anyway, let's see if my WIP code, which focuses mini windows on mouse hover, will do any good on this < https://gist.github.com/richardgv/5696281 >. (Note it adds dependency on libpng, libjpeg{,-turbo}, and giflib, which are installed on most desktop systems.) Specifically, please tell me if it prints out something like this:

mainwin_map(): Failed to grab keyboard (1), troubles ahead.

[richardgv]

When the options movePointerOn* are disabled, fvwm sometimes believes we are stealing focus and tries to revert the focus back, which messes things up, but I've seen no other problems. I'm closing this issue. Please reopen it if you still see the problem with the latest version.