On some devices, only certain buttons will wake up the gamepad API (the shapes on PS3 controllers, for instance) Close other apps that may be using the gamepad. Some things to check: Is the device plugged in / connected via bluetooth. Is there a way to elevate this topic to Citrix Development? I think it would be wise to some kind of "translate" the mouse button bindings from the actual client OS to the actual vDisk OS in order to have the "normal" mouse button behavior of the vDisk OS. The Gamepad API is still inconsistent across browsers and OSes. Or maybe one reconfigured the settings for whatever reason, that person surely don't want to change the settings every time when using a virtual target. More so since I am not responsible of the client OS and version of all the users client machines.Ĭhanging the standard behavior is not the best choice if one needs this behavior when working on the client OS. This was done only for investigation purposes. Since the middle mouse button is essential for the AutoCAD users disabling the middle mouse button is not an option. This means after deactivating the middle mouse button on the linux client, there was also no middle mouse button in the target virtual machine. Xinput set - button - map "" 1 0 3 4 5 6 7 8 9 10 11 12 13 14 ^ |-> this is the mapping of the middle mouse button ( button2 ) ( to deactivate set to 0 )Īfter that the action in AutoCAD changed from "_pasteblock" (see picture of thread start which is standard behavior in Linux (paste marked text)) to "nothing". To get the mouse model in Ubuntu (xinput must be installed):įor testing purposes I deactivated the middle-mouse-button (in my case button 2): Unfortunately, I am not able to remap the button only for the particular device.After some more research I found out that it is actually the mouse bindings of the client OS that take effect in the virtual target.įor testing purposes I modified the bindings of the mouse buttons on the Ubuntu client using xinput: May be related to Bug 91571 - xkb set via xkbcomp does not seem to apply to -i (or does not stick if used on general device). When I press the Windows button on my USB keyboard (remapped to VOL+) and then on the mouse, it is interpreted as VOL+. The weird thing is, when I press the Windows button on the laptop's built-in keyboard (not remapped) and then on mouse, it is interpreted as Windows button. Then I tried remapping the Windows key (swapped with ) on my USB keyboard (id=9) using the second approach (pure xkbcomp) and it worked, BUT also changed behavior of the mouse's button in the same way (regardless how was the button mapped for the mouse). But without success, mouse's Windows key is still interpreted as Windows key. I have also tried similar approach described in Remap/change your secondary/usb keyboard keys. Setxkbmap -device $remote_id -print | sed 's/\(xkb_symbols.*\)"/\1+custom(remote)"/' | xkbcomp -I/tmp/xkb -i $remote_id -synch - $DISPLAY 2>/dev/null # remap Windows button on MS Sculpt Mouse to Back buttonĬat >/tmp/xkb/symbols/custom Xinput list | sed -n 's/.*Microsoft Sculpt Comfort Mouse.*id=\(*\).*/\1/p' I would do it using setxkbmap tool (described in How to remap keys under Linux for a specific keyboard only). Now, I need to remap the key for this particular device to another key. ↳ AT Translated Set 2 keyboard id=14 Īccording to xinput test 12 the Super_L key (keycode 133) is generated by the mouse when the "Windows button" is pressed on the mouse. ⎜ ↳ FocalTechPS/2 FocalTech FocalTech Touchpad id=15 ⎜ ↳ Microsoft Sculpt Comfort Mouse id=12 "Back" button) on my Linux machine (Linux Mint 18.2 "Sonya").Īccording to xinput list, the mouse is recognized as a pointer device (id=12). I would like to remap the "Windows button" on MS Sculpt Comfort Mouse to another button (eg. Right, so assuming that the installation went well, you should get a printout to the terminal when running xinput -test idofthestylus.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |