(In)Ability to wire graphic tablet stylus buttons in hyprland.lua keybinds section. #16393
Unanswered
Whistrock
asked this question in
Bugs - Input
Replies: 3 comments 1 reply
1 reply
|
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hyprland version
0.56.2 commit efb5099
Is this a regression?
No
What's the bug?
I seem to be unable to put in stylus inputs as they are not defined as a bind syntax(?).
For example look at this over here:
-- Move/resize windows with mainMod + LMB/RMB and dragging
hl.bind(mainMod .. " + mouse:272", hl.dsp.window.drag(), { mouse = true })
hl.bind(mainMod .. " + mouse:273", hl.dsp.window.resize(), { mouse = true })
I wish to be able to resize and move windows via stylus buttons as well. I got two here that I could utilize.
I have a Huion H430P working through kernel/libinput stack(?) (not proprietary huion driver or opentabletdriver)
This is the output of
libinput debug-eventsI attempt to put in the input I read here and there is no error but it does nothing.
Including the "s" letter seen in debut output (so it looked like mouse:s331) didn't help.
I try to change
mouse = truetomouse = falsebut that doesn't help either.I've also tried putting TABLET_TOOL_BUTTON directly to try my luck but it didn't help. I get unknown keysym.
Likewise I've tried my luck by changing "mouse" to "stylus" so it looked like "stylus:331" but I get the same unknown keysym.
Could it be possible to wire stylus buttons? Maybe a practical section in wiki as well to quickly identify such button names in a terminal in case that different styluses have different names.
I'm sorry if I'm missing something, please let me know.
Reproduction steps
Explained better in context in bug description unless my method is rather haphazard.
Attachments
No response
I acknowledge that:
I have searched all (open and closed) discussions and issues and my problem is not there.
I have read the Code of Conduct and agree to follow it.
I wrote this request with my own hands, my own keyboard, and in my own words.
All reactions