-
-
Notifications
You must be signed in to change notification settings - Fork 303
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
Pen button mappings do not work as expected #1250
Comments
Is the mapping done inside rnote or inside the gnome pen settings ? Can you share a screenshot of the settings page ? Might be related to #1104 (if a button is seen as an eraser, what's currently in the settings will have no effect and you'll have to keep the eraser pressed, draw, change the tool to the one you want then release the button currently). I have a PR to have this editable in the settings page (and also lock the mode of the eraser) |
Actually your first button on your stylus buttons does NOT act as a button but as a separate pen entirely when pressed (seen as an eraser most likely. Hence from the OS pov and rnote when you press it it detects an entirely different device !). Indeed
"pen_mode_state": {
"pen_mode": "pen",
"penmode_pen_style": "eraser",
"penmode_eraser_style": "eraser"
} Hence the two tools that are mapped to the two types of pens : pen and eraser. If you run rnote with So it's effectively #1104 (with #1119 to fix it though still some polish to do there). Do this :
To change the mapping for now |
Thanks, I was able to fix the mapping for now. I always thought that the two pens listed there is just because of the fact that I do have two physical pens, so that was confusing. |
Oh right I missed the "two physical pens" part. Maybe both have their first button mapped to the eraser (instead of ... you know, the first button). To me this is a bug/wrong mapping in libinput |
After fumbling around somewhat a little more, a third pen (based on the larger pen which has tilt and pressure) appeared on Gnome's setting panel, so I would assume your theory is true. Both pens behave the same in rnote though, and mapping the eraser to another tool in one pen also affects the other. |
I believe it isn´t. I have the same bug (HP Envy x360 with HP MPP pen) and I for once never had this bug with Xournal++ and while the bug occurs (rnote having first button mapped to pen instead of eraser), Xournal still functions as expected (button toggling eraser). |
Just to chime in, I recently had to dig into libwacom and the GNOME settings to get my pen and tablet working. From what I learnt this is kind of a Rnote issue but also, it isn't. Basically, Rnote maps the primary button action to what GNOME interprets as the right mouse button click, and the secondary action corresponds to the middle mouse button click. So, you have to set up your pens accordingly in your DE stylus settings for the actions to be mapped like you want them to.
If I understood your problem correctly, you just have to keep the eraser button pressed and while doing that switching to the eraser tool. Now every time the eraser should be active as long as you keep the button pressed. As already mentioned, this behaviour can't be changed by Rnote, this is a weird stylus firmware behaviour Microsoft enforced upon the manufacturers, and it is impossible for the OS to map something exclusively to this button. Every time one presses the eraser button, the stylus reports itself as leaving the proximity of the screen and a second totally unrelated pen entering the proximity. So libwacom has to handle that as two different pens in one, which is why the button can't just be mapped to something. You can check by running |
Describe the bug
By default, I have my button 1 mapped to eraser toggle, and button 2 to selection. However, as soon as I use either the shape or text tool, the mapping is changed to toggling that instead. The mapping options in the UI has no effect. The only way I can get my eraser back is by resetting all the data associated with rnote (
rm -rf .var/app/com.github.flxzt.rnote/
).To Reproduce
Steps to reproduce the behavior:
Expected behavior
The mapping should not change just by using a tool
Console Output
Run the app in the terminal with
flatpak --env=RUST_LOG=rnote=debug --env=RUST_BACKTRACE=1 run com.github.flxzt.rnote
and post the output.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Flatpak, Rnote 0.11.0, Gentoo running GNOME Wayland
X1 yoga 6th gen. Same result with both the built-in pen and an external Wacom AES pen.
The text was updated successfully, but these errors were encountered: