Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Weird behavior with scrollwheel #4

Closed
NerosTie opened this issue Dec 3, 2016 · 3 comments
Closed

Weird behavior with scrollwheel #4

NerosTie opened this issue Dec 3, 2016 · 3 comments

Comments

@NerosTie
Copy link

NerosTie commented Dec 3, 2016

On KDE, the scrollwheel has a weird behavior. When I alt+tab between windows, then I use the scrollwheel, it scrolls up when I want to scroll down the first time then it scrolls down…

If I use this script to deactivate the keyboard feature, it works as expected.

 
#!/bin/sh
DEVICE_ID=$(xinput list |  grep "Logitech G300s Optical Gaming Mouse" | grep keyboard | sed 's/.*id=\([0-9]*\).*/\1/')

if
    xinput -list-props $DEVICE_ID | grep "Device Enabled" | grep "1$" > /dev/null
then
    xinput set-int-prop $DEVICE_ID "Device Enabled" 8 0
fi

But… the extra buttons don't work anymore and I can't use ratslap with this solution.

Have you the same issue?
Do you have an idea for a solution?
Can ratslap do something about that?

Thank you!

EDIT: well, you know what? It seems I don't have this bug on Wayland. So, maybe, the best solution is to switch to Wayland when it will be better.

@krayon
Copy link
Owner

krayon commented Dec 5, 2016

I have tried to replicate in my WM (i3) without success. Sounds like an issue with KDE?

Once you disable the keyboard functionality then yes, the mouse cannot send keyboard events. It SHOULD however still work if you assign the buttons to mouse buttons ("button9" etc). Worst case you could do that and then have something listening for those buttons to generate keyboard events. It's a hack and a half but it'd work I'd say. There is a tool that can listen for those mouse buttons and do that but I don't recall it's name right now.

@krayon
Copy link
Owner

krayon commented Dec 5, 2016

Incidentally, my i3 instance is in X so if it's not purely a "KDE" issue it could be a "KDE in X" issue.

@NerosTie
Copy link
Author

NerosTie commented Mar 2, 2017

It's fixed and it was not related to ratslap.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants