But it would be interesting to know where the change took place.
And of course, this is just fine since it is the condition I want. The 2nd one works and seem to make the change permanent - I could not get back to a condition where the USB joysticks affected the mouse cursor. And again, please refer to the link (item 36) in my 1st post to see what I am trying to adapt for my use.įollowing are now two scripts which work without generating error msgs. Property Generate Key Events doesn't exist, you need to specify its type and formatĬan anyone suggest the syntax to eliminate these error msgs. Property Generate Mouse Events doesn't exist, you need to specify its type and format Ids=$(xinput list | grep "$NAME" | grep -o -e "id=." | xargs | sed "s/id=//g")īut even tho the code works, I get the two error msgs: #get NAME for controller from xinput list #use to disable mouse emulation from controller sticks(joysticks) And voilla, the cursor returns to normal behavior. The sequence: 1)open a terminal, 2)enter the script file on the cmd line, 3)plug in the rc-controller(see the mouse move to left), 4)with some skill get the uncooperative mouse cursor to pass over the terminal screen and click on it to make it active, 5)hit return to execute the script. The following code when executed "delinks" the mouse pointer from joystick movements. I looked at a lot of grep stuff, but could not determine the problem. I would appreciate a suggestion to where the syntax is in error. Xinput set-prop $id "Generate Key Events" 0 Xinput set-prop $id "Generate Mouse Events" 0 Ids=$(xinput list | grep $NAME | grep -o -e "id=." | xargs | sed "s/id=//g")Įcho "Disabling Mouse/Key events for ID $id" I substitute the name of my controller the script generates the error: "grep: PPM: No such file or directory" Now I want to adopt the script code in post #36 in the link. ↳ Microsoft Microsoft® Nano Transceiver v2.0 id=8 ⎜ ↳ Microsoft Microsoft® Nano Transceiver v2.0 id=10 ⎜ ↳ Microsoft Microsoft® Nano Transceiver v2.0 id=9 WAILLY PPM is my controller (and in this case its id =12, but it has also been xinput list In this case, the line "WAILLY PPM id=12 1st I run xinput list per below to obtain the controller name. However, as noted by post #36 in the link, the option numbers can change with each boot, thus to facilitate disabling, a script is in order that can be launched when necessary. I have successfully disabled per post #34 in the following link:
I am working towards disabling mouse emulation of USB rc plane controller when the controller is plugged in, it interferes with the mouse pointer.
0 kommentar(er)
