Add support for Wacom Movink

[flying-elephant]

Those commits are ready for Wacom Movink announced yesterday.

[whot]

Thanks for the quick PR - a few questions but otherwise this is almost ready.

[whot]

We can't have one button in two locations but based on the drawing this should be Top=C, right?

Also, after looking at some marketing pictures: are those real buttons or emulated by the driver (in userspace)? or rather: do we get those events under linux?

[flying-elephant]

Top=C, right?

I'll work on this, thanks!
There are two buttons on each sides, so I thought they should be the sides.
"Tpo=C" makes much sense.

Yes, one of the physical buttons can be assigned for an express key, but it also can be other functionalities than the express key; one of them is "Touch on/off".

[whot]

can be assigned for an express key,

so these are software/firmware controlled buttons? that's going to be ... interesting, libwacom doesn't have a good way to express these for now.

Might be best to add a comment in the file here and then figure out how to really handle this later when we have the consumers (e.g. mutter + gnome-control-center) actually wanting deal with these buttons.

[github-actions]

Hi, there. I'm a bot and have been asked to have a look at this.

Please run the sysinfo script from https://github.com/linuxwacom/wacom-hid-descriptors and
file a new issue in that repo with the resulting sysinfo tarball. The README in that repo
has more information and instructions.

The .tablet files in this PR should then link to the sysinfo in this form:

# sysinfo.abCdE1234.tar.gz
# https://github.com/linuxwacom/wacom-hid-descriptors/issues/1234

A git grep sysinfo will show how this is currently used in existing data files.

See also https://github.com/linuxwacom/libwacom/wiki/Adding-a-new-device

---

This is an automated comment created by a bot. Responding to the bot or mentioning it won't have any effect.

[whot]

can be assigned for an express key,

so these are software/firmware controlled buttons? that's going to be ... interesting, libwacom doesn't have a good way to express these for now.

Might be best to add a comment in the file here and then figure out how to really handle this later when we have the consumers (e.g. mutter + gnome-control-center) actually wanting deal with these buttons.

[whot]

Thanks for the update. CI still fails so at least two changes are still needed - please make sure to run meson test -C builddir locally, that'll run (most of) the test suite locally so it'll speed up finding the various nitpicks my human eyes won't see :)

[flying-elephant]

I modified the codes and updated them.
However, I got the attached log by running the suggestion, "meson test -C".
Do you know what is wrong exactly?
The log looks like the lines which describe about the eraser button, but I'm not sure what I should do.
"UD pen" could have an eraser button, so it has to stick with it somehow.
testlog.txt

[whot]

I think the eraser parsing fails, fixing that should fix the CI

[whot]

All good now, let's get this merged! Thanks heaps for the effort

[github-actions]

Hi, there. I'm a bot and have been asked to have a look at this.

Thanks for providing the sysinfo. Someone will be along shortly to review the PR.

---

This is an automated comment created by a bot. Responding to the bot or mentioning it won't have any effect.