Stefan Klinger <fvwm....@stefan-klinger.de> writes:
> Dan Espen (2018-Nov-06, excerpt):
>> Looks to me like Fvwm thinks your mouse 1 button has the Mod 4 modifier
>> active.
>
> If so, then why does FVWM not try to move the window around, unless
> the Super key is actually held down?
>
>> Have you done something to enable sticky modifier keys?
>
> Not that I'd be aware of. If “sticky modifier keys” means the feature
> to press and release a modifier, and preserve the modifiers effect for
> the next keypress, then no, I do not have such a feature. Also,
> {num,scroll,caps}lock are off.
>
>> You might want run "xev" and press mouse 1.
>
> Okay, but I'm a little overwhelmed by the output. I've used
>
> $ FvwmCommand 'mouse 1 A 4 moveOrRaise' # bind
> $ xev > bound.txt
>
> and
>
> $ FvwmCommand 'mouse 1 A 4' # unbind
> $ xev > unbound.txt
>
> to create the attached files. The ButtonPress, ButtonRelease, and
> KeymapNotify events look pretty similar to me.
>
> I have even restarted X with all my keyboard and mouse settings (via
> `xkbcomp` and `xinput`) disabled, but that has no effect on the error.
The part I was after is this:
ButtonRelease event, serial 33, synthetic NO, window 0x1200001,
root 0x1cf, subw 0x0, time 3086503, (119,138), root:(766,139),
state 0x100, button 1, same_screen YES
^^^^^
I did this:
FvwmCommand 'mouse 1 A 4 Beep'
Then I used xev to capture the press with the "Windows" key held down:
ButtonRelease event, serial 36, synthetic NO, window 0x2e00001,
root 0x24d, subw 0x0, time 1095056384, (125,80), root:(1539,1094),
state 0x140, button 1, same_screen YES
^^^^^
Running this way, Fvwm beeps when I press button 1 with the Windows key
held down.
So, I'm unclear why Fvwm is reacting to mouse 1 on your system
as if modifier 4 is active. Xev is showing it non-active.
I can't tell why you don't see the effect of Fvwm running "moveOrRaise"
since I can't see your function definition. Maybe you should share
that.
--
Dan Espen
