* AJ MacLeod -- Thursday 26 January 2006 13:28: > Which leads me to a linked question; is there any way of assigning nasal > functions to joystick buttons on a per-aircraft basis (i.e. with the > _aircraft_ setting the controls, not the JS config), in the same way the > keyboard can be remapped?
Yes, kind of: there are several wrapper functions in controls.nas that individual aircraft can redefine. Some are doing that already. We could use more of these wrappers. For example, the joystick configs just call controls.lowerFlap(0), and controls.nas defines what lowerFlap() means. You can redefine that in your aircraft for special flap handling (see the Hurricane config). But as long as your aircraft has flaps, you may only use that for flap handling! Everything else would be a big mistake. Aircraft may only redefine *how* things are done, but not on which of my js buttons they are done. Aircraft know *nothing* about my joystick, or my preferences. > I've replicated this with a bit of nasal, which now works - but is the only > way to use this to have every user temporarily and manually change their JS > config? If you are missing a redefinable wrapper in controls.nas, then write one (and adapt all js configs for it). m. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
