O.K. The following code when executed "delinks" the mouse pointer from
joystick movements. 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. And voilla, the cursor returns to normal behavior.

Code:

#!/bin/bash
#file:  script_rccontroller.sh
#use to disable mouse emulation from controller sticks(joysticks)
#get NAME for controller from xinput list

NAME='WAILLY PPM'

ids=$(xinput list | grep  "$NAME" | grep -o -e "id=.." | xargs | sed "s/id=//g")
for id in $ids; do
    echo "Disabling Mouse/Key events for ID $id"
    xinput set-prop $id "Generate Mouse Events" 0
    xinput set-prop $id "Generate Key Events" 0
done

But even tho the code works, I get the two error msgs:
property Generate Mouse Events doesn't exist, you need to specify its type and 
format
property Generate Key Events doesn't exist, you need to specify its type and 
format

Can anyone suggest the syntax to eliminate these error msgs. And again,
please refer to the link (item 36) in my 1st post to see what I am
trying to adapt for my use.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/418470

Title:
  USB Gamepad detected as mouse (Speedlink 360 style)

Status in “xserver-xorg-input-evdev” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: xserver-xorg-input-evdev

  Hi !

  My USB gamepad is controlling both the mouse pointer AND the joystick
  (in rrootage for instance) at the same time.

  To get it running at all I had to :

  - install xserver-xorg-input-joystick
  - copy acrux-usb-gamepad-8116.fdi to /etc/hal/fdi/policy (provided here : 
https://help.ubuntu.com/community/Joystick_lshal_outputs_done )
  - unplug and replug the joystick after the X server is loaded

  Those three steps are apparently mandatory otherwise nothing works.
  (the stick LED doesn't remain lit otherwise)

  Actually it raises several issues !
  1. the need for the the aforementioned steps
  2. the need to unplug / replug
  3. the fact that evdev seems to lock the controller and assign it as if it 
were a mouse

  Thanks a lot for reading this, 
  cheers !

  Attached : lshal output, where the gamepad does seem to be detected
  properly.

  Setup : Ubuntu 9.04, AMD64

  ProblemType: Bug
  Architecture: amd64
  DistroRelease: Ubuntu 9.04
  NonfreeKernelModules: nvidia
  Package: xserver-xorg-input-evdev 1:2.1.1-1ubuntu4
  ProcEnviron:
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersion: Linux version 2.6.28-15-generic (buildd@yellow) (gcc version 
4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #49-Ubuntu SMP Tue Aug 18 19:25:34 UTC 2009
  SourcePackage: xserver-xorg-input-evdev
  Uname: Linux 2.6.28-15-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/418470/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to