Thomas Adam

Hi @NsCDE That's odd -- I most definitely do not see this in my testing. I wonder what other setting(s) you have which could impact this?

Hi @NsCDE Your first point is correct -- as I've mentioned, focus events for monitors can only happen on windows which are focused, not the root window. I think the...

Hey @NsCDE, I still cannot get `-1` -- but I suspect that could be resolved by a few commits found on `ta/gh-604`, if you could test that, please? Here's the...

Hi @NsCDE With your example, things continue to work exactly as they should -- I do not see any delays or missing events from either `enter_window` or `monitor_focus`. Very strange.

Hi @NsCDE Can you try `ta/gh-604` again, please? I've added a single line to print the event options sent to fvwm to stderr -- so for you to see this,...

Hi @NsCDE Yes -- you'll see `-1` for `monitor_*` events due to them not having a window-context to operate on. As for why you don't see *any* `monitor_focus` events with...

Hmm... $[monitor.prev] will be blank if you've never focused a window on a different monitor. Just focusing the root window doesn't count, remember. If I just use the default config,...

What fvwm3 version are you using? For me: ``` % ./fvwm/fvwm3 --version fvwm3 1.0.5 (1.0.4-149-g34906f73f) ```

The problem is `NeverFocus` -- I bet if you put a window on top of the FvwmButtons instance, and used that to focus the cursor between monitors, that things start...

OK -- I've added a few things and rebased `ta/gh-604` -- please retest.