[winswitch] Scrolling with mouse wheel not working

[Lukas Haase]

Hi Antoine,

Thanks for your quick response!

> On 03/02/17 04:17, Lukas Haase via shifter-users wrote:
> > Hi,
> > 
> > When I use my mouse wheel, the up direction seems to be ignored, scrolling down works.
> > An easy way to reproduce is to start midnight commander (mc) in xterm and go into a large directory. I can scroll down with my mouse wheel but not up.
> > 
> > Is this some known issue or an unknown bug?
> > 
> > In case it matters: I use xpra client 1.0 (14502) under Win 10 and xpra v1.0.1-r14734 under CentOS 5.
> Are you sure that you are using the 1.x branch on CentOS 5?
> I don't see how you could have installed it.

You are right - it is CentOS 6 ;-)

> [...]
> You can try running the client with "-d mouse" and you should see events
> like those:
> _button_action(4, ...
> (4 for up and 5 for down. 6 for left and 7 for right)

Ok. When I use scroll up using the mouse wheel I get tons of these messages:

2017-02-02 17:28:29,496 mousewheel: orientation=vertical distance=30.0, units=0, new value=0.0, keys=0x0, x=439, y=360, client=gtk2.client, wid=218

When I scrool down (the one that works) the messages are slightly different:

2017-02-02 17:29:41,362 mousewheel: send 1 wheel events to the server for distance=-120, remainder=0
2017-02-02 17:29:41,382 mousewheel: orientation=vertical distance=-30.0, units=-1, new value=-30.0, keys=0x0, x=434, y=375, client=gtk2.client, wid=218

> [...]
> Your next step would be to run an application like "xev" to verify that
> the events are seen by the X11 client applications.

Yes, here seems to be the problem. Scrolling down:

ButtonPress event, serial 36, synthetic NO, window 0xc00001,
    root 0x25d, subw 0x0, time 1389734833, (177,154), root:(445,445),
    state 0x0, button 5, same_screen YES

ButtonRelease event, serial 36, synthetic NO, window 0xc00001,
    root 0x25d, subw 0x0, time 1389734833, (177,154), root:(445,445),
    state 0x1000, button 5, same_screen YES


Scrolling up: No messages!

Do I interpret it correctly that the client does not forward the "up wheel" messages to the server (since there is no "send 1 wheel events to the server ..." for up scrolling?
 

Thanks,
Luke