2009/3/16 Dominik Vogt <[email protected]>: > On Sun, Mar 15, 2009 at 06:08:19PM -0700, Jason Weber wrote: > [snip] >> > 1. Key polling >> > >> > I'm not completely sure what the current code does. I assume the >> > keyboard map is polled every time an event occurs. However, there >> > may be a possibility that the keyboard map changed but no event >> > occurs. >> > >> > Earlier versions polled at a regular interval, which was >> > inacceptable. >> > >> > We have to test this: >> > >> > * Invoke FvwmProxy by pressing a modifier key and configure it to >> > terminate when the key is released. >> > * Don't touch the mouse from now and make sure that no events >> > occur that effect FvwmProxy. >> > * Open a menu with the keyboard; fvwm grabs the keyboard. Make >> > sure that the menu window does not overlap any FvwmProxy >> > windows. >> > * Release the modifier key inside the menu. >> > * Close the menu by pressing Escape. >> > >> > Now, does FvwmProxy close or not? If so, the current polling of >> > the keyboard map works acceptably. >> >> Yes, at the very end. >> >> (no touching the mouse) >> Meta3-ESC: proxies up >> Meta3-M: custom menu with some window ops pops up (proxies still up) > >> Release Meta3: nothing happens > > As expected while the keyboard is grabbed.
I've had problems with FvwmProxy; I don't configure anything, but bind the "showtoggle" option to a key. If I have two windows one stacked on the other and group them, if I then focus between them with FvwmProxy running (none of the proxy windows need to be visible, it's enough to just have "Module FvwmProxy" loaded), FVWM (I assume) get's in a continuous lopp constantly shifting focus between the two windows which are stacked. I wonder if this is due to the default behaviour of WIndowListFunc somehow? [...] -- Thomas Adam
