[TabletButtonHandling]: GUI improved (button mapping) + tablet buttons informations sent to the driver#62
Conversation
Variable with the model tablet recognized by the driver
Added a KeepTipDown command, which sets how long the pen tip output state should be kept down after the tip button is released.
…ons to the driver
|
As I said, tablet buttons are currently not working and I need some help to detect tablet buttons, but all tablet informations are currently stocked in the Tablet class. I also have some local work about sending global input keypresses but this is really easy to implement so it'll be okay ! |
…ed buttonMap driver-side
… VirtualKey value
|
I've tried to use USBlyzer to look at the tablet interfaces as you said last week but I didn't find anything that can help me to handle tablet buttons (+ it's my first approach with this kind of project tbh). I might need some help about that, and I'm also fixing some issues when shortcuts are triggered, I'll fix then do a PR again asap |
|
@Shoko84 I renamed the hidDevice2 to hidDeviceAux. I've also added code which reads the data from the HID auxiliary device. |
2 participants
Button mapping has been improved GUI-side
Tablet buttons informations are sent correctly to the driver (backend)
Keyboard macros are also sent correctly to the driver (macros not working tho for now)
This first version should be working theoretically but since nothing has been touched about buttons clicking and pen movements, it should be fine.
Tablet buttons are not working for now and this branch is in WIP, but all help is welcome !