On Fri, 13 Jul 2007, Holger Wirtz wrote: > That redefinition would be great (because there is not need for me > patching the keyboard.xml for the PTT key anymore :-) ). > > This makes it possible for fgcom to switch through the COMs and NAVs - > something like a switchboard simulation. I am currently implementing the > code for this feature in fgcom. After finishing you can switch through > COM1, NAV1, COM2 and NAV2 (if you select the NAVs with a VOR-frequency > you get the morsecode of the NAV name) if they are serviceable. > > BTW: Is there is any code that uses the "serviceable" property from the > COMs and NAVs? > > And a little bit of this topic: Is there an easy way to show the > selected COM/NAV (e.rgb. printing the selected COM/NAV for 5 seconds on > the screen)?
Hi! If you use nasal you can display a "tooltip" by calling gui.popupTip(), e.g. print_wow = func { gui.popupTip("Current weight on gear " ~ getprop(weight_on_gear) ~ " lbs."); } I think it might also be nice to use a nasal wrapper for the PTT key binding (like most things in controls.nas), that way a user could more easily add more bindings for PTT (e.g. a joystick button). Cheers, Anders -- --------------------------------------------------------------------------- Anders Gidenstam mail: anders(at)gidenstam.org WWW: http://www.gidenstam.org/FlightGear/JSBSim-LTA/ ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel