A few enhancements#53
Conversation
CNB-Kevin
left a comment
There was a problem hiding this comment.
Crash at line 317 of huion-tablet-driver.py when the user only has 1 monitor.
|
There is an issue where if you turn off the driver (I run it in a terminal and use ctrl+C while I'm testing things) if multi-cursor is enabled (which it is by default). Leftover cursors can stay on screen or appear/disappear. It could be user error on my part because I turn it off, but it's also caused by the lack of cleanup at the end of the program, which is also a thing on the main branch. |
|
Yes, multi-cursor on X is not reliable. There a bit of cleanup in the code when the driver is started again but it would be better to do it at the end of program, if there were a cleanup procedure before exiting. |
Introduces a constant so that users can specify their output monitor for calibrate_mapping(). This expands on the bug fix mentioned here joseluis#53 (comment)
Create constant XOUTPUT_DEVICE_ARGUMENT to control calibrate_mapping
|
I finally had the opportunity to test the clean up code for multi-cursor (the tablet is 6000 km from my computer!). Leftover cursors when the driver is interrupted shouldn't remain on the screen and X should be more stable now. |
|
hey! first of all thank you for this miracle! everything is ok except i still have the residual pointers in my tablet. also while drawing i get a round semi transparent box around the cursor. and i have two residuals cursors on my tablet after i end the script that keep flickering. aaand while it works there is always one inactive cursor on the side of the tablet. so i have one moving with the mouse.one with the pen and one that just sits there. also even if i set multi cursor to false its still enabled oh sorry 18.04 version! |
|
My daughter who owns the tablet told me she has the same behaviour from time to time. She told me that there could be a conflict with Firefox too but I don't have the details. And I can't debug, only when I go and visit my daughter far from home... |
|
Could it be that the calibration of the tablet is not correct? |

This merge requests adds a few enhancements: