search

ther0n / UnnaturalScrollWheels

Invert scroll direction for physical scroll wheels while maintaining "Natural" scrolling for trackpads on MacOS
GNU General Public License v3.0
3.39k stars 73 forks source link

Wacom support #31

Open carlcalderon opened 3 years ago

carlcalderon commented 3 years ago

Expected behavior: Scrolling with a Wacom device should be left unmodified / ignored by UnnaturalScrollWheels.

Actual behavior: UnnaturalScrollWheels intercepts the Scroll/Pan functionallity from the Wacom device and amplifies the scrolling speed.

Description: I don't perceive my Wacom Intous Pro M a "scroll wheel" and did not expect UnnaturalScrollWheels to cause any problems. However, it seems like the application acts upon the scrolling generated by the Wacom device whilst scrolling using the Wacom pencil with the Scroll/Pan modifier active.

Suggestion: If possible; add a checkbox to the settings panel by which the user can toggle Wacom interception on or off. This could maybe be extended to allow the user to pick target devices from a list.

Sidenotes: Thank you for an awesome application!

ther0n commented 2 years ago

I don't think there's really anything I can do about this, the app works by intercepting all scroll events and checking which values are or are not present in the event. There might be a way to check the name or something of the device that is sending the event. But that would require checking the name of the device every scroll event which would increase the code complexity as well as increasing the resource requirements by quite a bit and hurt battery life. I can look at adding a check box to except certain devices but it might could end up being a lot of code. I do agree that a wacom tablet should have "natural" scrolling but it must be sending standard mouse scroll wheel events rather than touchpad events as the trackpad and Magic Mouse do.

carlcalderon commented 2 years ago

I see. This issue is probably somewhat related to https://github.com/ther0n/UnnaturalScrollWheels/issues/7. As you say, major changes are most likely required in order to detect software and/or devices that override features in specific ways.

May I suggest a 2.0.0 version label or similar to highlight this issue as "future"?