I have just commited basic support for the linux event devices. It is disabled by default and has to be enabled by calling ./configure --with-eventinput (Don't forget autogen.sh before that) If enabled, FlightGear needs dbus-1 and hal devel packages for the headers and libs.
The system is not complete, yet. The hotplug support is still missing, there is no support for Mac and Win. The configure script is not perfect: no checking for required packages dbus-1-devel and hal-devel is done. Probably switches --with-dbus-1= and --with-hal= should be added to make the paths for the libs configurable. I can't guarantee that everything works flawless, but it should compile clean and shouldn't break your system. At least, if it's disabled ;-) For usage, check the data/Input/Event/3dconnexion/SpaceNavigator.xml as an example how to configure your devices. The bindings work as they do in other parts of FlightGear. New is the <setting> section for sending events to the device. One should easily find out, how they work by looking at the sample device. If you want to find out which input devices are supported by your linux these two commands are your friends: $ cat /proc/bus/input/devices or $ lshal Have fun playing with it - Please report bugs or ask questions. Torsten ------------------------------------------------------------------------------ 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
