You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When one initiates a scroll (with touch or trackpad) it is possible to start drawing while continuing to scroll. This can be quite annoying when one mistakenly starts to scroll just before writing because of poor palm rejection. It seems that it also applies to inertial scrolling.
Describe the solution you'd like
It would be nice to be able to stop any scrolling when the pen gets near / start drawing.
Describe alternatives you've considered
I've looked into disabling the touchscreen entirely, but it doesn't seem possible either.
Additional context
Palm rejection is a difficult problem (but I must say that I'm amazed how well it works already) this should help sidestep the issue.
The text was updated successfully, but these errors were encountered:
This add a buton on the header (next to the focus mode) that deactivate all touch event (that I couls find) on the canvas. Therefore the app will ignore any incorrect touch input (due to poor palm rejection) while keeping the touch capabilities for the rest of the app.
This is my first time ever modifying a GTK app, so I'm assuming I broke many thing.
Is your feature request related to a problem? Please describe.
When one initiates a scroll (with touch or trackpad) it is possible to start drawing while continuing to scroll. This can be quite annoying when one mistakenly starts to scroll just before writing because of poor palm rejection. It seems that it also applies to inertial scrolling.
Describe the solution you'd like
It would be nice to be able to stop any scrolling when the pen gets near / start drawing.
Describe alternatives you've considered
I've looked into disabling the touchscreen entirely, but it doesn't seem possible either.
Additional context
Palm rejection is a difficult problem (but I must say that I'm amazed how well it works already) this should help sidestep the issue.
The text was updated successfully, but these errors were encountered: