Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PTK-640 limited script functionality on Fedora 29 #24

Open
heviiguy opened this issue Dec 10, 2018 · 2 comments
Open

PTK-640 limited script functionality on Fedora 29 #24

heviiguy opened this issue Dec 10, 2018 · 2 comments

Comments

@heviiguy
Copy link

In my quest to find something to help me obtain proper functionality of the centre ring button I installed your package. "Proper" meaning the ability to scroll through 4 options so that, at least, I can control brush size as well as zoom with the "RingUp" and "RingDown. Alas, this doesn't seem to be possible.
Furthermore, the "Keystroke..." functionality when trying to set a stroke with a keypad input does not register. Too bad because this seems to provide the only option to set Labels for the buttons.

@tb2097
Copy link
Owner

tb2097 commented Dec 11, 2018

The issue with the centre button states in that it isn't something supported at the driver level. I have some initial designs on how this could be added as a feature, but given the major changes I have made to the interface I want to ensure everything is in a stable state before marking it as such and working on trying to implement additional features. For example, I would need to do some research to determine how to enable the LEDs that let you know what configuration is currently set, which I'm unsure if they are addressable in Linux. I did find someone's code specific to the PTK-640 that can address the LEDs (and the icons displayed beside the buttons), however I don't have one to test with and it doesn't seem to work with the devices I do have.

With the keypad input, the mapping should be working correctly, however what it does is dependent on the state of your NumLock, as it would be using the real keyboard. The driver sends the keypress signal, which I am unable to override. You can check that it is being set as the correct keypad key.
ie. if you map button B to keypad Delete:

Wacom Intuos Pro M Finger touch 	id: 10	type: TOUCH     
Wacom Intuos Pro M Pen stylus   	id: 11	type: STYLUS    
Wacom Intuos Pro M Pen eraser   	id: 12	type: ERASER    
Wacom Intuos Pro M Pen cursor   	id: 13	type: CURSOR    
Wacom Intuos Pro M Pen pad      	id: 14	type: PAD
> xsetwacom --get 14 button 2
key +KP_Delete -KP_Delete```
with NumLock on, it with print `.`, with it off it will function as the delete key.

@tb2097
Copy link
Owner

tb2097 commented Feb 8, 2019

It looks like the people behind libwacom tools are starting to work on something to work with the monitoring/configuring of toggle. I'll monitor/see what I can help with in this regard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants