python-evdev icon indicating copy to clipboard operation
python-evdev copied to clipboard

How can I see device mode?

Open jave opened this issue 10 months ago • 2 comments

I have a wacom expresskey, it hs 3 leds, and a mode button. With the mode button i can change which mode led lights up.

When I use libinput debug-events, I can see the mode:

event3 TABLET_PAD_BUTTON +2.128s 0 pressed (mode 0) event3 TABLET_PAD_BUTTON +2.356s 0 released (mode 0) event3 TABLET_PAD_BUTTON +2.780s 0 pressed (mode 1) event3 TABLET_PAD_BUTTON +3.040s 0 released (mode 1) event3 TABLET_PAD_BUTTON +3.916s 0 pressed (mode 2) event3 TABLET_PAD_BUTTON +4.124s 0 released (mode 2)

However, I cant seem to read the mode from python code. Is it possible?

jave avatar Feb 16 '25 00:02 jave

What does evtest show?

ssieb avatar Feb 16 '25 01:02 ssieb

Event: time 1739721167.779586, -------------- SYN_REPORT ------------
Event: time 1739721167.923731, type 1 (EV_KEY), code 256 (BTN_0), value 0
Event: time 1739721167.923731, type 3 (EV_ABS), code 40 (ABS_MISC), value 0
Event: time 1739721167.923731, type 4 (EV_MSC), code 0 (MSC_SERIAL), value 354310
Event: time 1739721167.923731, -------------- SYN_REPORT ------------
Event: time 1739721168.023158, type 1 (EV_KEY), code 256 (BTN_0), value 1
Event: time 1739721168.023158, type 3 (EV_ABS), code 40 (ABS_MISC), value 15
Event: time 1739721168.023158, type 4 (EV_MSC), code 0 (MSC_SERIAL), value 354310
Event: time 1739721168.023158, -------------- SYN_REPORT ------------
Event: time 1739721168.123145, type 1 (EV_KEY), code 256 (BTN_0), value 0
Event: time 1739721168.123145, type 3 (EV_ABS), code 40 (ABS_MISC), value 0
Event: time 1739721168.123145, type 4 (EV_MSC), code 0 (MSC_SERIAL), value 354310
Event: time 1739721168.123145, -------------- SYN_REPORT ------------
Event: time 1739721168.195652, type 1 (EV_KEY), code 256 (BTN_0), value 1
Event: time 1739721168.195652, type 3 (EV_ABS), code 40 (ABS_MISC), value 15
Event: time 1739721168.195652, type 4 (EV_MSC), code 0 (MSC_SERIAL), value 354310
Event: time 1739721168.195652, -------------- SYN_REPORT ------------
Event: time 1739721168.311111, type 1 (EV_KEY), code 256 (BTN_0), value 0
Event: time 1739721168.311111, type 3 (EV_ABS), code 40 (ABS_MISC), value 0
Event: time 1739721168.311111, type 4 (EV_MSC), code 0 (MSC_SERIAL), value 354310
Event: time 1739721168.311111, -------------- SYN_REPORT ------------
Event: time 1739721168.399148, type 1 (EV_KEY), code 256 (BTN_0), value 1
Event: time 1739721168.399148, type 3 (EV_ABS), code 40 (ABS_MISC), value 15
Event: time 1739721168.399148, type 4 (EV_MSC), code 0 (MSC_SERIAL), value 354310
Event: time 1739721168.399148, -------------- SYN_REPORT ------------
Event: time 1739721168.471177, type 1 (EV_KEY), code 256 (BTN_0), value 0
Event: time 1739721168.471177, type 3 (EV_ABS), code 40 (ABS_MISC), value 0
Event: time 1739721168.471177, type 4 (EV_MSC), code 0 (MSC_SERIAL), value 354310
Event: time 1739721168.471177, -------------- SYN_REPORT ------------

So in this case i dont see any device mode information, so its different than libinput debug-events.

jave avatar Feb 16 '25 15:02 jave