Running on wayland about userspace-tablet-driver-daemon

[albfan]

It's suppose the using libei, or a tool that uses lbei: https://gitlab.freedesktop.org/libinput/libei/

something like uinput would also work, but it's lower level

@kurikaesu any tips of where to implement this? I'm tempted to detect wayland using "XDG_SESSION_TYPE" env var and use this library to send keys

[kurikaesu]

Interesting. I've tested my tablets under wayland and the express/shortcut keys appear to work correctly. Granted, I have not done this anytime recently. I wonder if it is because the KD100 is not being identified as a keyboard device. With xorg/X11 the configuration files force the device to be handled by libinput.

[albfan]

I own a HS611 and default customization provided by GNOME mostly works (it just miss some side bar keys and upper scroll)

for KD100

looks it behaves as no driver mode when just connected,

https://support.huion.com/en/support/solutions/articles/44002245976-huion-mini-keydial-kd100-faqs

although it doesn't match for me. It exposes:
k1 Ctrl+Z
k2 Ctrl+Shift+Z
k5 Ctrl+Space
k6 F5

rest of keys and dial are empty.

I need to clear any setup I made rm ~/.local/share/userspace_tablet_driver_daemon/driver.cfg or no key works for me.

I understand from lsusb:

Bus 001 Device 005: ID 256c:006d

I need to rework something on src/huion_handler.cpp but not sure where

and using your userspace server it outputs

[albfan]

hmm looks like it is behaving as keystrokes for GNOME tablet:

it only exposes 8 keys, while this device has 16 square buttons + two large buttons + dial + 1 mouse button

still your userspace server + wayland looks interesting to implement to me

[albfan]

Finally I found two problems:

• wayland integration is done with libwacom on GNOME OS.
• connection:

  • wired connection this device expose

    Bus 001 Device 006: ID 256c:006d HUION Huion Tablet_HS611

  • but through usb dongle

    Bus 001 Device 005: ID 256c:006d

my approach was to expose how you detect real device through wireless usb dongle (firmware) to libwacom:

linuxwacom/libwacom#469

I think expose device through a common library api allows to deal with devices easily. What do you think?

Still able to collaborate here to add wayland support if you need. Reopen if you want to see it implemented, probably a general issue (implement wayland support is a better idea and this would be just a use case to test)