[Bug]: Pen issues on linux-surface

[apmyplol]

What happened?

I noticed a couple of bugs while trying out this very promising program on my linux device.
I noticed that my surface pen is not working when trying to draw, but erasing and selection etc works fine.
When doing the pointer test in the settings it recognizes my pens tip as Input 1, but does not recognize any pressure (pressure is constantly 0). I believe this might be the reason for why drawing does not work with the pen.
Moreover I noticed that the pointer test doesn't recognize the eraser at the back of the pen (Input number is 1) and that the functional button on the pen is recognized as 4 when hovering over the device and as 5 when touching the device with the pen. This makes it impossible to map them, because in the settings its only possible to map 1 and 2.

Other programs (rnote) recognize the eraser correctly.
Im using a surface device with the linux-surface kernel installed. Maybe this problem only appears on linux-surface devices.

Version

2.2.0

Platform

Linux

Relevant log output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[CodeDoctorDE]

Sadly, the first issue looks like a known bug, see #238.
The mapping of button 4 and 5 looks just like a small enhancement which i could add.
(kTertiaryButton is 4).
5 is when both 4 + 1 (kTeritaryButton + primary button) was clicked...

Btw: Which type does it say on the pointer test when touching with the stylus?

[apmyplol]

For me, the pen also works like before (i.e. everything except writing with the pen tool) when enabling pen only input.
The pointer test also says pen correctly, when I use the pen.
The fact that the pen input only doesn't work for the drawing tool feels like its maybe unrelated to the issue you mentioned.

[CodeDoctorDE]

Quick question: does the button value ever be 0 when having the pen on it?
Otherwise i would just remap the settings a bit that pen input = 1, first button = 2 and second button = 4

[CodeDoctorDE]

fixed in 2.2.1-rc.1,
I use now bit masks instead of == (it's okay if you don't understand this :)), this should improve multi button handling and i'm now priorizing the secondary button over the primary button.

[apmyplol]

Thank you very much for the quick fix. It will be implemented in the nightly build soon, right? Ill test it out then.

Quick question: does the button value ever be 0 when having the pen on it? Otherwise i would just remap the settings a bit that pen input = 1, first button = 2 and second button = 4

No, the input is only 0 when the pen doesnt touch the device.

[CodeDoctorDE]

Yes it will be available in the next nightly Version next Monday with many other fixes.

That's good, then you don't need to change any settings and it will work out of the box in the next nightly.