[PD] mousestate

Hans-Christoph Steiner hans at eds.org
Thu Apr 24 06:54:55 CEST 2003


On Wed, 23 Apr 2003, vanDongen-Gilcher wrote:

> Hans-Christoph Steiner said at "RE: [PD] mousestate."r[2003/04/22 19:46]

> > - [rawjoystick] uses the Linux input event system, rather than the older
> > joystick interface, but that shouldn't make a visible difference.  
> > 
> If you have configured the input layer in the kernel, /dev/js* is linked to 
> /dev/input/js*, so 
> [joystick] already uses the input layer.

I meant I use it directly...  [rawjoystick] uses /dev/input/event?, as
does [rawmouse] and [rawevent].  /dev/input/js? wouldn't work with
[rawjoystick] because of the different datatypes.
 
> > - [rawjoystick] has a fixed number of outlets, [joystick]'s outlets
are 
> > dynamically
> > generated.
> 
> That is curious, I think a inputlayer aware joystick driver announces its 
> axis to the input layer.

I mean that if your joystick has 18 axes, then [joystick] will have 18
outlets for those axes, while [rawjoystick] will always have the same 6
outlets for axes.  I did this to prevent the patch from breaking if you
attach a different joystick.

> Although I think a  HID joystick does it incorrectly, at least I always had 
> the maximum number (18) axis

I got a response from Vojtech Pavlik (Mr Linux HID) about
this.  Apparently, the HID drivers in linux 2.4 detect force-feedback 
devices as axes, thereby reporting the wrong number of axes.  My joystick 
reports 41 axes under linux.  It supposedly fixed in 2.5, but 2.5 is a major 
pain to install.

> > - [rawjoystick] supports a hat switch.  (My joystick only has one, so
> > that's what I based it on....)
> > 
> At least for my joystick, this is allready the case. The hat switches are 
> mapped to 2 additional axis'

Well, I've only tested any of these objects on my one joystick, so...
 
> But the polling should be an improvement.

Did you have problems with the polling latency of [joystick]?  I ask
because I am have started writing these same objects based on libSDL and
it looks like it would be easier to use a clock_delay like [joystick]
rather than the allpollfn like [rawjoystick]. 

Could I ask about your ff joystick setup?  I am using a Saitek Cyborg 3D
Force with linux 2.4.21-pre2-ff and I can't get the force feedback
working.  Plus linux HID reports it has 41 axes and 16 buttons (it has 6
axes and 9 buttons).


.hc


	zen
	   \
	    \
	     \





More information about the Pd-list mailing list