Dear All,
The active area of my new drawing tablet is half of the available one. How can one set the active area to full?
Thanks in advance,
Paul
On 2021-09-13 11:31 a.m., Paul Smith wrote:
The active area of my new drawing tablet is half of the available one. How can one set the active area to full?
Can you explain in more detail what you mean?
Here's something to test. Run "evtest" and pick the tablet. Before you do anything, there should be a list of what it supports. For example, part of mine shows this: Event type 3 (EV_ABS) Event code 0 (ABS_X) Value 13067 Min 0 Max 32767 Resolution 323 Event code 1 (ABS_Y) Value 19156 Min 0 Max 32767 Resolution 430
Check the min and max numbers for yours and then move the stylus to the corners and see if the position matches. The input system should automatically scale the resulting values to match your display. Do you have more than one screen?
On Mon, Sep 13, 2021 at 8:27 PM Samuel Sieb samuel@sieb.net wrote:
The active area of my new drawing tablet is half of the available one. How can one set the active area to full?
Can you explain in more detail what you mean?
Here's something to test. Run "evtest" and pick the tablet. Before you do anything, there should be a list of what it supports. For example, part of mine shows this: Event type 3 (EV_ABS) Event code 0 (ABS_X) Value 13067 Min 0 Max 32767 Resolution 323 Event code 1 (ABS_Y) Value 19156 Min 0 Max 32767 Resolution 430
Check the min and max numbers for yours and then move the stylus to the corners and see if the position matches. The input system should automatically scale the resulting values to match your display. Do you have more than one screen?
Thanks, again, Samuel. I have only one screen.
By sliding my hand with the pen on the tablet, I reach the right border of the screen when I am in the middle of my drawing tablet. Ideally, the screen border should be reached only when the pen gets close to the tablet border -- that is what I mean.
My "evtest" does not report Event type 3 (EV_ABS). Please, see below what is reported:
Select the device event number [0-19]: 18 Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6161 product 0x4d15 version 0x111 Input device name: "LetSketch LetSketch" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 1 (KEY_ESC) Event code 2 (KEY_1) Event code 3 (KEY_2) Event code 4 (KEY_3) Event code 5 (KEY_4) Event code 6 (KEY_5) Event code 7 (KEY_6) Event code 8 (KEY_7) Event code 9 (KEY_8) Event code 10 (KEY_9) Event code 11 (KEY_0) Event code 12 (KEY_MINUS) Event code 13 (KEY_EQUAL) Event code 14 (KEY_BACKSPACE) Event code 15 (KEY_TAB) Event code 16 (KEY_Q) Event code 17 (KEY_W) Event code 18 (KEY_E) Event code 19 (KEY_R) Event code 20 (KEY_T) Event code 21 (KEY_Y) Event code 22 (KEY_U) Event code 23 (KEY_I) Event code 24 (KEY_O) Event code 25 (KEY_P) Event code 26 (KEY_LEFTBRACE) Event code 27 (KEY_RIGHTBRACE) Event code 28 (KEY_ENTER) Event code 29 (KEY_LEFTCTRL) Event code 30 (KEY_A) Event code 31 (KEY_S) Event code 32 (KEY_D) Event code 33 (KEY_F) Event code 34 (KEY_G) Event code 35 (KEY_H) Event code 36 (KEY_J) Event code 37 (KEY_K) Event code 38 (KEY_L) Event code 39 (KEY_SEMICOLON) Event code 40 (KEY_APOSTROPHE) Event code 41 (KEY_GRAVE) Event code 42 (KEY_LEFTSHIFT) Event code 43 (KEY_BACKSLASH) Event code 44 (KEY_Z) Event code 45 (KEY_X) Event code 46 (KEY_C) Event code 47 (KEY_V) Event code 48 (KEY_B) Event code 49 (KEY_N) Event code 50 (KEY_M) Event code 51 (KEY_COMMA) Event code 52 (KEY_DOT) Event code 53 (KEY_SLASH) Event code 54 (KEY_RIGHTSHIFT) Event code 55 (KEY_KPASTERISK) Event code 56 (KEY_LEFTALT) Event code 57 (KEY_SPACE) Event code 58 (KEY_CAPSLOCK) Event code 59 (KEY_F1) Event code 60 (KEY_F2) Event code 61 (KEY_F3) Event code 62 (KEY_F4) Event code 63 (KEY_F5) Event code 64 (KEY_F6) Event code 65 (KEY_F7) Event code 66 (KEY_F8) Event code 67 (KEY_F9) Event code 68 (KEY_F10) Event code 69 (KEY_NUMLOCK) Event code 70 (KEY_SCROLLLOCK) Event code 71 (KEY_KP7) Event code 72 (KEY_KP8) Event code 73 (KEY_KP9) Event code 74 (KEY_KPMINUS) Event code 75 (KEY_KP4) Event code 76 (KEY_KP5) Event code 77 (KEY_KP6) Event code 78 (KEY_KPPLUS) Event code 79 (KEY_KP1) Event code 80 (KEY_KP2) Event code 81 (KEY_KP3) Event code 82 (KEY_KP0) Event code 83 (KEY_KPDOT) Event code 86 (KEY_102ND) Event code 87 (KEY_F11) Event code 88 (KEY_F12) Event code 96 (KEY_KPENTER) Event code 97 (KEY_RIGHTCTRL) Event code 98 (KEY_KPSLASH) Event code 99 (KEY_SYSRQ) Event code 100 (KEY_RIGHTALT) Event code 102 (KEY_HOME) Event code 103 (KEY_UP) Event code 104 (KEY_PAGEUP) Event code 105 (KEY_LEFT) Event code 106 (KEY_RIGHT) Event code 107 (KEY_END) Event code 108 (KEY_DOWN) Event code 109 (KEY_PAGEDOWN) Event code 110 (KEY_INSERT) Event code 111 (KEY_DELETE) Event code 119 (KEY_PAUSE) Event code 125 (KEY_LEFTMETA) Event code 126 (KEY_RIGHTMETA) Event code 127 (KEY_COMPOSE) Event type 4 (EV_MSC) Event code 4 (MSC_SCAN) Event type 17 (EV_LED) Event code 0 (LED_NUML) state 1 Event code 1 (LED_CAPSL) state 0 Event code 2 (LED_SCROLLL) state 0 Event code 3 (LED_COMPOSE) state 0 Event code 4 (LED_KANA) state 0 Key repeat handling: Repeat type 20 (EV_REP) Repeat code 0 (REP_DELAY) Value 250 Repeat code 1 (REP_PERIOD) Value 33 Properties: Testing ... (interrupt to exit)
On 2021-09-13 12:59 p.m., Paul Smith wrote:
On Mon, Sep 13, 2021 at 8:27 PM Samuel Sieb samuel@sieb.net wrote:
Check the min and max numbers for yours and then move the stylus to the corners and see if the position matches. The input system should automatically scale the resulting values to match your display. Do you have more than one screen?
Thanks, again, Samuel. I have only one screen.
By sliding my hand with the pen on the tablet, I reach the right border of the screen when I am in the middle of my drawing tablet. Ideally, the screen border should be reached only when the pen gets close to the tablet border -- that is what I mean.
Ok, then it sounds like something is getting the wrong dimensions. Are you using Gnome?
My "evtest" does not report Event type 3 (EV_ABS). Please, see below what is reported:
Select the device event number [0-19]: 18
There must be another device for it then. Maybe 19?
On Mon, Sep 13, 2021 at 10:14 PM Samuel Sieb samuel@sieb.net wrote:
Check the min and max numbers for yours and then move the stylus to the corners and see if the position matches. The input system should automatically scale the resulting values to match your display. Do you have more than one screen?
Thanks, again, Samuel. I have only one screen.
By sliding my hand with the pen on the tablet, I reach the right border of the screen when I am in the middle of my drawing tablet. Ideally, the screen border should be reached only when the pen gets close to the tablet border -- that is what I mean.
Ok, then it sounds like something is getting the wrong dimensions. Are you using Gnome?
My "evtest" does not report Event type 3 (EV_ABS). Please, see below what is reported:
Select the device event number [0-19]: 18
There must be another device for it then. Maybe 19?
Thanks, Samuel. My fault. The correct one reports the following:
Select the device event number [0-19]: 5 Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6161 product 0x4d15 version 0x111 Input device name: "LetSketch LetSketch" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 320 (BTN_TOOL_PEN) Event code 321 (BTN_TOOL_RUBBER) Event code 330 (BTN_TOUCH) Event code 331 (BTN_STYLUS) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value 0 Min 0 Max 32767 Resolution 152 Event code 1 (ABS_Y) Value 0 Min 0 Max 32767 Resolution 244 Event code 24 (ABS_PRESSURE) Value 0 Min 0 Max 8191 Event type 4 (EV_MSC) Event code 4 (MSC_SCAN) Properties: Property type 1 (INPUT_PROP_DIRECT) Testing ... (interrupt to exit)
On 2021-09-13 2:23 p.m., Paul Smith wrote:
Select the device event number [0-19]: 5 Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6161 product 0x4d15 version 0x111 Input device name: "LetSketch LetSketch" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 320 (BTN_TOOL_PEN) Event code 321 (BTN_TOOL_RUBBER) Event code 330 (BTN_TOUCH) Event code 331 (BTN_STYLUS) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value 0 Min 0 Max 32767 Resolution 152 Event code 1 (ABS_Y) Value 0 Min 0 Max 32767 Resolution 244
Now if you move the stylus to all the corners, what range of values do you get?
On Mon, Sep 13, 2021 at 10:32 PM Samuel Sieb samuel@sieb.net wrote:
Select the device event number [0-19]: 5 Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6161 product 0x4d15 version 0x111 Input device name: "LetSketch LetSketch" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 320 (BTN_TOOL_PEN) Event code 321 (BTN_TOOL_RUBBER) Event code 330 (BTN_TOUCH) Event code 331 (BTN_STYLUS) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value 0 Min 0 Max 32767 Resolution 152 Event code 1 (ABS_Y) Value 0 Min 0 Max 32767 Resolution 244
Now if you move the stylus to all the corners, what range of values do you get?
Samuel: When I move the stylus on the right-hand side of the tablet no ABS-X coordinate is reported; only ABS-Y keeps changing. This may be the problem, but I do not know how to solve it.
When I move the stylus on the left-hand side of the tablet, both coordinates (ABS-X and ABS-Y) keep changing!
Paul
On 9/13/21 2:40 PM, Paul Smith wrote:
On Mon, Sep 13, 2021 at 10:32 PM Samuel Sieb samuel@sieb.net wrote:
Now if you move the stylus to all the corners, what range of values do you get?
Samuel: When I move the stylus on the right-hand side of the tablet no ABS-X coordinate is reported; only ABS-Y keeps changing. This may be the problem, but I do not know how to solve it.
What is the maximum value it gets to? Also, do you mean that there's only an ABS-Y in the packet? It sounds like either the tablet isn't reporting correctly or the kernel hid driver is interpreting it incorrectly. Are there any relevant messages in the journal.
Something I just discovered is an application called "hidviz". It directly talks to the device over the HID interface and shows what it finds. Try running it and select the interface for the stylus. Copy the output from the Descriptor View and then watch the values in the Device View as you move the stylus around, particularly in the right side.
On Mon, Sep 13, 2021 at 11:44 PM Samuel Sieb samuel@sieb.net wrote:
Now if you move the stylus to all the corners, what range of values do you get?
Samuel: When I move the stylus on the right-hand side of the tablet no ABS-X coordinate is reported; only ABS-Y keeps changing. This may be the problem, but I do not know how to solve it.
What is the maximum value it gets to? Also, do you mean that there's only an ABS-Y in the packet? It sounds like either the tablet isn't reporting correctly or the kernel hid driver is interpreting it incorrectly. Are there any relevant messages in the journal.
Something I just discovered is an application called "hidviz". It directly talks to the device over the HID interface and shows what it finds. Try running it and select the interface for the stylus. Copy the output from the Descriptor View and then watch the values in the Device View as you move the stylus around, particularly in the right side.
Thanks, Samuel. I do not have the drawing tablet here where I am now, but later on I will report the results given by hidviz.
While sliding the stylus horizontally from the left to the right, the screen cursor moves accordingly, but the right border of the screen is reached when the stylus is in the middle of the drawing tablet. Maybe, for some strange reason, my drawing tablet considers there are two screens and not a single one. How can we test that?
Paul
On 2021-09-14 12:08 a.m., Paul Smith wrote:
While sliding the stylus horizontally from the left to the right, the screen cursor moves accordingly, but the right border of the screen is reached when the stylus is in the middle of the drawing tablet. Maybe, for some strange reason, my drawing tablet considers there are two screens and not a single one. How can we test that?
The table knows nothing. :-) It has a certain range of values and the input layer takes that and the display size and should map the values accordingly. So something is going wrong and that's what I'm hoping to find out with the hidviz program.
On Tue, Sep 14, 2021 at 8:37 AM Samuel Sieb samuel@sieb.net wrote:
While sliding the stylus horizontally from the left to the right, the screen cursor moves accordingly, but the right border of the screen is reached when the stylus is in the middle of the drawing tablet. Maybe, for some strange reason, my drawing tablet considers there are two screens and not a single one. How can we test that?
The table knows nothing. :-) It has a certain range of values and the input layer takes that and the display size and should map the values accordingly. So something is going wrong and that's what I'm hoping to find out with the hidviz program.
Thanks, Samuel. When the stylus is on the middle of my drawing tablet,
ABS-X = 30693 (approximately).
When the stylus is on the lower right corner, hidviz padding input shows
X = 2 and Y=2.
From hiviz, I get yet the following:
---------------------------------- Usage Page (Digitizer) Usage (Pen) Collection (Application) Report ID (10) Usage (Stylus) Collection (Physical) Usage (Tip Switch) Usage (Barrel Switch) Usage (Eraser) Usage (Invert) Usage (Secondary Tip Switch) Usage (Barrel Switch) Logical minimum (0) Logical maximum (1) Report size (1) Report count (6) Item Usage (In Range) Report size (1) Report count (1) Item Item Usage Page (Generic Desktop) Usage (X) Usage (Y) Unit exponent (-3) Unit (51) Logical maximum (32767) Physical minimum (0) Physical maximum (2048) Report size (16) Report count (2) Item Usage Page (Digitizer) Usage (Tip Pressure) Logical maximum (8191) Report size (16) Report count (1) Item End Collection End Collection
On Tue, Sep 14, 2021 at 2:34 PM Paul Smith phhs80@gmail.com wrote:
While sliding the stylus horizontally from the left to the right, the screen cursor moves accordingly, but the right border of the screen is reached when the stylus is in the middle of the drawing tablet. Maybe, for some strange reason, my drawing tablet considers there are two screens and not a single one. How can we test that?
The table knows nothing. :-) It has a certain range of values and the input layer takes that and the display size and should map the values accordingly. So something is going wrong and that's what I'm hoping to find out with the hidviz program.
Thanks, Samuel. When the stylus is on the middle of my drawing tablet,
ABS-X = 30693 (approximately).
When the stylus is on the lower right corner, hidviz padding input shows
X = 2 and Y=2.
From hiviz, I get yet the following:
Usage Page (Digitizer) Usage (Pen) Collection (Application) Report ID (10) Usage (Stylus) Collection (Physical) Usage (Tip Switch) Usage (Barrel Switch) Usage (Eraser) Usage (Invert) Usage (Secondary Tip Switch) Usage (Barrel Switch) Logical minimum (0) Logical maximum (1) Report size (1) Report count (6) Item Usage (In Range) Report size (1) Report count (1) Item Item Usage Page (Generic Desktop) Usage (X) Usage (Y) Unit exponent (-3) Unit (51) Logical maximum (32767) Physical minimum (0) Physical maximum (2048) Report size (16) Report count (2) Item Usage Page (Digitizer) Usage (Tip Pressure) Logical maximum (8191) Report size (16) Report count (1) Item End Collection End Collection
Does the above give you some clue, Samuel?
Paul
On 2021-09-14 6:34 a.m., Paul Smith wrote:
On Tue, Sep 14, 2021 at 8:37 AM Samuel Sieb samuel@sieb.net wrote:
While sliding the stylus horizontally from the left to the right, the screen cursor moves accordingly, but the right border of the screen is reached when the stylus is in the middle of the drawing tablet. Maybe, for some strange reason, my drawing tablet considers there are two screens and not a single one. How can we test that?
The table knows nothing. :-) It has a certain range of values and the input layer takes that and the display size and should map the values accordingly. So something is going wrong and that's what I'm hoping to find out with the hidviz program.
Thanks, Samuel. When the stylus is on the middle of my drawing tablet,
ABS-X = 30693 (approximately).
What happens as you move further to the right? Try moving slowly across the middle.
When the stylus is on the lower right corner, hidviz padding input shows
X = 2 and Y=2.
From hiviz, I get yet the following:
Usage Page (Digitizer) Usage (Pen) Collection (Application)
Is this the same section that you see active values in? For my tablet, the active values are in this section: Usage Page (Generic Desktop) Usage (Mouse) Collection (Application) Report ID (9) Usage (Pointer) Collection (Physical)
Do you have that section? If so, what does it have in it?
On Fri, Sep 17, 2021 at 8:34 AM Samuel Sieb samuel@sieb.net wrote:
While sliding the stylus horizontally from the left to the right, the screen cursor moves accordingly, but the right border of the screen is reached when the stylus is in the middle of the drawing tablet. Maybe, for some strange reason, my drawing tablet considers there are two screens and not a single one. How can we test that?
The table knows nothing. :-) It has a certain range of values and the input layer takes that and the display size and should map the values accordingly. So something is going wrong and that's what I'm hoping to find out with the hidviz program.
Thanks, Samuel. When the stylus is on the middle of my drawing tablet,
ABS-X = 30693 (approximately).
What happens as you move further to the right? Try moving slowly across the middle.
Thanks, Samuel. Please, see below.
When the stylus is on the lower right corner, hidviz padding input shows
X = 2 and Y=2.
From hiviz, I get yet the following:
Usage Page (Digitizer) Usage (Pen) Collection (Application)
Is this the same section that you see active values in? For my tablet, the active values are in this section: Usage Page (Generic Desktop) Usage (Mouse) Collection (Application) Report ID (9) Usage (Pointer) Collection (Physical)
Do you have that section? If so, what does it have in it?
I have the following:
------------------------------------- Usage Page (Generic Desktop) Usage (Mouse) Collection (Application) Report ID (1) Usage (Pointer) Collection (Physical) Usage Page (Button) Usage Minimum (Button 1) Usage Maximum (Button 5) Logical minimum (0) Logical maximum (1) Report count (5) Report size (1) Item Report count (1) Report size (3) Item Usage Page (Generic Desktop) Usage (X) Usage (Y) Logical minimum (-2047) Logical maximum (2047) Report size (12) Report count (2) Item Usage (Wheel) Logical minimum (-127) Logical maximum (127) Report size (8) Report count (1) Item Usage Page (Consumer) Usage (AC Flip Vertical) Report count (1) Item End Collection End Collection ------------------------------------- Event: time 1631875096.010113, type 3 (EV_ABS), code 0 (ABS_X), value 32767 Event: time 1631875096.010113, type 3 (EV_ABS), code 1 (ABS_Y), value 22055 Event: time 1631875096.010113, -------------- SYN_REPORT ------------ Event: time 1631875096.110119, type 3 (EV_ABS), code 1 (ABS_Y), value 22037 Event: time 1631875096.110119, -------------- SYN_REPORT ------------ Event: time 1631875096.124127, type 3 (EV_ABS), code 1 (ABS_Y), value 22016 Event: time 1631875096.124127, -------------- SYN_REPORT ------------ Event: time 1631875096.136106, type 3 (EV_ABS), code 1 (ABS_Y), value 21999 Event: time 1631875096.136106, -------------- SYN_REPORT ------------ Event: time 1631875096.150107, type 3 (EV_ABS), code 1 (ABS_Y), value 21977 Event: time 1631875096.150107, -------------- SYN_REPORT ------------ [...] Event: time 1631875100.124584, -------------- SYN_REPORT ------------ Event: time 1631875100.130573, type 3 (EV_ABS), code 1 (ABS_Y), value 21562 Event: time 1631875100.130573, -------------- SYN_REPORT ------------ Event: time 1631875100.136587, type 3 (EV_ABS), code 1 (ABS_Y), value 21570 Event: time 1631875100.136587, -------------- SYN_REPORT ------------ Event: time 1631875100.194589, type 3 (EV_ABS), code 1 (ABS_Y), value 21587
On Fri, Sep 17, 2021 at 11:45 AM Paul Smith phhs80@gmail.com wrote:
While sliding the stylus horizontally from the left to the right, the screen cursor moves accordingly, but the right border of the screen is reached when the stylus is in the middle of the drawing tablet. Maybe, for some strange reason, my drawing tablet considers there are two screens and not a single one. How can we test that?
The table knows nothing. :-) It has a certain range of values and the input layer takes that and the display size and should map the values accordingly. So something is going wrong and that's what I'm hoping to find out with the hidviz program.
Thanks, Samuel. When the stylus is on the middle of my drawing tablet,
ABS-X = 30693 (approximately).
What happens as you move further to the right? Try moving slowly across the middle.
Thanks, Samuel. Please, see below.
When the stylus is on the lower right corner, hidviz padding input shows
X = 2 and Y=2.
From hiviz, I get yet the following:
Usage Page (Digitizer) Usage (Pen) Collection (Application)
Is this the same section that you see active values in? For my tablet, the active values are in this section: Usage Page (Generic Desktop) Usage (Mouse) Collection (Application) Report ID (9) Usage (Pointer) Collection (Physical)
Do you have that section? If so, what does it have in it?
I have the following:
Usage Page (Generic Desktop) Usage (Mouse) Collection (Application) Report ID (1) Usage (Pointer) Collection (Physical) Usage Page (Button) Usage Minimum (Button 1) Usage Maximum (Button 5) Logical minimum (0) Logical maximum (1) Report count (5) Report size (1) Item Report count (1) Report size (3) Item Usage Page (Generic Desktop) Usage (X) Usage (Y) Logical minimum (-2047) Logical maximum (2047) Report size (12) Report count (2) Item Usage (Wheel) Logical minimum (-127) Logical maximum (127) Report size (8) Report count (1) Item Usage Page (Consumer) Usage (AC Flip Vertical) Report count (1) Item End Collection End Collection
Event: time 1631875096.010113, type 3 (EV_ABS), code 0 (ABS_X), value 32767 Event: time 1631875096.010113, type 3 (EV_ABS), code 1 (ABS_Y), value 22055 Event: time 1631875096.010113, -------------- SYN_REPORT ------------ Event: time 1631875096.110119, type 3 (EV_ABS), code 1 (ABS_Y), value 22037 Event: time 1631875096.110119, -------------- SYN_REPORT ------------ Event: time 1631875096.124127, type 3 (EV_ABS), code 1 (ABS_Y), value 22016 Event: time 1631875096.124127, -------------- SYN_REPORT ------------ Event: time 1631875096.136106, type 3 (EV_ABS), code 1 (ABS_Y), value 21999 Event: time 1631875096.136106, -------------- SYN_REPORT ------------ Event: time 1631875096.150107, type 3 (EV_ABS), code 1 (ABS_Y), value 21977 Event: time 1631875096.150107, -------------- SYN_REPORT ------------ [...] Event: time 1631875100.124584, -------------- SYN_REPORT ------------ Event: time 1631875100.130573, type 3 (EV_ABS), code 1 (ABS_Y), value 21562 Event: time 1631875100.130573, -------------- SYN_REPORT ------------ Event: time 1631875100.136587, type 3 (EV_ABS), code 1 (ABS_Y), value 21570 Event: time 1631875100.136587, -------------- SYN_REPORT ------------ Event: time 1631875100.194589, type 3 (EV_ABS), code 1 (ABS_Y), value 21587
I have meanwhile filed a bug regarding this issue:
https://bugzilla.redhat.com/show_bug.cgi?id=2005575
Paul
-
Paul Smith -
Samuel Sieb