I have xdotools installed
when making my button layout in .shuttle-go.json i come across some weired (or at least for me unclear behaviours).
i tried to keep the keynames from ym local /usr/include/X11/keysymdef.h (but found out that you made them availeable wihout the XK_ trough the definitions.go)
interesting is that sometimes it needs the XK_ to make the button work sometimes not,...and i do not understand the pattern behind it........do you have any idea ?......i use a german keyboardlayout on my keayboard if that plays any role in that..
here are some bindings i trie with a comment if they wok or not
"bindings": {
"F1": "XF86AudioMute //works",
"F2": "Micmute // doesnt work",
"M1+F2": "Control+Shift+F12 //Bildschirm aus // works",
"F3": "XF86MonBrightnessDown //works",
"F4": "XF86MonBrightnessUp //works",
"M1+F1": "XF86AudioMedia // doesnt work",
"F5": "XF86AudioRewind // doesnt work",
"F6": "XF86AudioPrev // doesnt work",
"F7": "PlayPause //Play oder XF86AudioPlay // doesnt work",
"F8": "NextSong // XF86AudioNext // both do not work",
"F9": "Forward // XF86XKAudioForward // both do not work",
"M1": "ScrollDown // doesnt work",
"M2": "XK_Scroll_Up/D // doesnt work",
"B1": "Control+F10 //Fenster aller Arbeitsflächen zeigen //works",
"B2": "Control+Shift+y // Zwischenablage anzeige //works",
"B3": "Control+Shift+Tab // zwischen Aktivitäten wechseln //works",
"B4": "Control+Shift+d // Desktop anzeigen //works",
"B3+F2": "XF86MonBrightnessUp // works",
"B3+F1": "XF86MonBrightnessDown // works",
"JogL": "XF86AudioLowerVolume // leiser // works",
"JogR": "XF86AudioRaiseVolume // lauter // works",
"S-7": "shift+Left // fastrewind in sayonara // works",
"S-1": "Control+minus // zoomout //works",
"S1": "Control+plus // zoomin // doesnt work",
"S7": "shift+Right // fastforward in sayonara // works"
}
},
Via the Shuttlo-go debugging all the Buttons show the "right" xdotool key definitions
interesting is that if i try xev | grep --line-buffered keysym
only the shuttle-buttons that work correct get printed
state 0x0, keycode 36 (keysym 0xff0d, Return), same_screen YES,
state 0x0, keycode 173 (keysym 0x1008ff16, XF86AudioPrev), same_screen YES,
state 0x0, keycode 176 (keysym 0x1008ff3e, XF86AudioRewind), same_screen YES,
state 0x0, keycode 176 (keysym 0x1008ff3e, XF86AudioRewind), same_screen YES,
state 0x0, keycode 233 (keysym 0x1008ff02, XF86MonBrightnessUp), same_screen YES,
state 0x0, keycode 232 (keysym 0x1008ff03, XF86MonBrightnessDown), same_screen YES,
state 0x0, keycode 121 (keysym 0x1008ff12, XF86AudioMute), same_screen YES,
state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
pressing for expample
"M1": "ScrollDown // doesnt work",
"M2": "XK_Scroll_Up/D // doesnt work",
does not print anything with xev | grep --line-buffered keysym
I guess my understanding and basic knowledge is on the Limit here.
So i say Thanks for some Support
I have xdotools installed
when making my button layout in .shuttle-go.json i come across some weired (or at least for me unclear behaviours).
i tried to keep the keynames from ym local /usr/include/X11/keysymdef.h (but found out that you made them availeable wihout the XK_ trough the definitions.go)
interesting is that sometimes it needs the XK_ to make the button work sometimes not,...and i do not understand the pattern behind it........do you have any idea ?......i use a german keyboardlayout on my keayboard if that plays any role in that..
here are some bindings i trie with a comment if they wok or not
Via the Shuttlo-go debugging all the Buttons show the "right" xdotool key definitions
interesting is that if i try
xev | grep --line-buffered keysymonly the shuttle-buttons that work correct get printed
pressing for expample
does not print anything with
xev | grep --line-buffered keysymI guess my understanding and basic knowledge is on the Limit here.
So i say Thanks for some Support