From time to time, the focused window ignores keybindings to iconify/maximize etc. the window. Other keybindings like --behavior works fine. My terminal (urxvt) blinks, like if the keystroke was sent to the application (eg. -i). Clicking in the window, or changing to another one and back makes it react on the keybindings again.
It can happen to all applications, and I haven’t been able to track down any system in it.
Anybody got at clue?
Key I WT 4 Iconify
Key M WT 4 Maximize
Key Left WT 4 Move w-50p w+0
Key Right WT 4 Move w+50p w+0
Key Up WT 4 Move w+0 w-50p
Key Down WT 4 Move w+0 w+50p
No FvwmEvent, L25 is in config, other modifiers doesn’t work as well, and my code is nicely formatted, at least when the forum doesn’t convert tabs into spaces…
I found out that it happens every time i switch windows using a WindowList. See relevant code below. Don’t know why I couldn’t find out when it happened earlier. So after switching to a window using --etc., it ignores window-managing keybindings. Maybe something to do with window focusing?
I apologize that I was too fast with the first post. With this clarification, can anybody give me a hint?
Hmm… It happens with all my applications; even if I use the default config from FvwmForm-Setup from another user account. Maybe it has something to do with my Xorg-config or xmodmap, I don’t know. At least it works now…
I have written a more accurate description in the bug report. You still can’t reproduce it?
I’m on those mailing lists, remember. I might not reply, but I did read your email. Other than spending no more than about a minute with this, it’s not something I want to look into. Let someone else on the mailing list do all the hard work.
Cursory at least, this doesn’t seem like a proper fix at all for what is probably a completely different problem anyway.
In case anybody gets the same issue: The window buttons are not a part of the window title. So the “WT” context in the keybindings I used should be extended to include the visible buttons, in my case “WT1246”.