On Tuesday 04 August 2009 19:54:23 Torsten Dreyer wrote: > I am currently playing with the input subsystem. This was triggered because > I have two devices that currently do not work with FlightGear, neither > Linux nor Windows. > My idea is to extend the FGInput class so it can use the devices presented > thru the event interface. While at it, I'd also like to add hotplug support > for devices, plugged in or out while FlightGear runs. > What do you think? Are the new features worth introducing new dependencies > and platform dependent modules?
I'm really pleased to see someone looking at this - I think it's an area where the current way of doing things is beginning to creak and no longer ideal. As you probably recall I found this last year when I switched to a Saitek X52 Pro stick/throttle/MFD setup with a significant number of buttons, axes and controllable LEDs. Brief thread from the time... http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg18466.html While I did eventually manage (with help from various quarters) to hack together enough parts to make everything on the stick work pretty much as I wanted, and the amazing flexibility of FG (which usually seems to provide several workarounds for any given problem) was highlighted, the process was far from optimal. Personally, I'd be very much in favour of this development; the dependencies are hardly exotic on either the Windows or Linux side and presumably something similar is readily available on OSX. Cheers, AJ ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
