You are not logged in.
Pages: 1
Hey, thanks for bearing with the newbie questions.
So I have to connect for a Windows 10 machine through Citrix to run a game engine, usually the control scheme (think Blender or 3DS Max) would involve holding down the middle mouse button and moving the mouse to move the camera about the world. I've noticed that middle mouse clicking and dragging doesn't really seem to do anything in Linux, from what I've read that's because it's bound to paste. Is there a way I could rebind the middle mouse behaviour to effectively replicate that of a Windows machine?
I'd tried setting up autoscroll through xorg config, but that didn't really seem to change anything, although I could scroll by clicking in the mouse wheel in Firefox so I'm pretty sure it was working.
Thanks!
Last edited by Prio (2022-03-29 08:03:29)
Offline
I don't have a solution, but I can give input that I think you may be looking in the wrong direction. The middle mouse button is not bound to anything in any global sense as aluded to in your post. It is very common for X11 client programs to respond to a middle mouse button click as a paste action (it's a defacto standard even) but it is still up to each individual client program. And even in programs that do respond to a middle click in this way, it would not prevent middle-mouse drag actions.
Middle-mouse drag actions can and do work in linux and under X11 (or wayland). So your problem is that the client program (e.g., Citrix) is simply not responding to that input properly and / or not passing it on to the windows machine properly. Your troubleshooting should focus there: on how to get Citrix to handle these mouse events properly. While I have no experience at all with Citrix, I suspect changing your title to include that may get the attention of those who can help.
Last edited by Trilby (2022-03-28 19:56:15)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
So your problem is that the client program (e.g., Citrix) is simply not responding to that input properly and / or not passing it on to the windows machine properly. Your troubleshooting should focus there: on how to get Citrix to handle these mouse events properly.
You are absolutely correct, I did find a fix in the Citrix config. Post with the fix I used is in this thread. Simply invovled going to /opt/Citrix/ICAClient/config/All_regions.ini and then changing the line which states MouseSendsControlV=* to MouseSendsControlV=false. Hope it helps someone .
Offline
Just chiming in here to mention this helped me as well, but the Citrix stuff follows a hierarchy of configuration files so you can also change this on a user level by modifying ~/.ICAClient/wfclient.ini instead of the global All_Regions.ini.
This should be preferred since All_Regions.ini sets the defaults for all regions (hence the name) and you can override both on a region level and on a user level. MouseSendsControlV=* in All_Regions.ini has the highest precedence and configures the option so it can be changed by downstream config files. If you set it to false there instead of the user config files, you make it impossible for your users to choose other options (if this is a multiuser system).
More info: https://docs.citrix.com/en-us/citrix-wo … ences.html
Last edited by Psy-Q (2024-10-19 06:17:01)
Offline
Pages: 1