I've never looked at the kernel source. Presumably this would be a
trivial fix, no?
As always, write it and see.. :)
A keyboard can be interrogated. A mouse outputs constant data and/or can be interrogated. A standard joystick does.. nothing. It can look like it's there when it's not, and it can look like it isn't when it is. And there are more than a few different formats of joystick, do you plan to load every possible driver, checking all the time, and then dump the ones not in use? What if they have TWO joysticks? Pick the one that moves? What if they hit the other one while picking up the one they want?
How does your own software propose to reliably determine something that approaches near indeterminability? Trying to do this automatically will cause as many problems as it fixes. The USB can probably be done though, since it should have an ID string. You need to hurry up and write it, what is taking you so long?
As always, everything seems quite 'trivial' to those who haven't actually tried to do it. Hurry up and build a running robot too while you're at it..
Alan
_______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
