Oh, sorry. Forgot this one ... * John Denker -- Wednesday 04 July 2007: > I can see making another mode, to serve another purpose, such > as debugging joysticks, and /four/ digits would be worthwhile > in that case. It would be simple to put a mode-change button > on the existing popup.
I'd assume that debugging joysticks would be the main use of the dialog. We often tell people on IRC to use js_test and js_demo(.exe) for that, or the HUD. But the HUD isn't in all aircraft and doesn't have numbers attached, so the dialog might be a good idea. I don't think that it will be used much by people who forgot their trimming and want to look it up in flight. They could probably not make much sense of the values, anyway. "If I disengage the AP now with elevator trim 0.45, will it 'kill' me?" Numbers are probably not that much help for the pilot in this case. A mode-change button would IMHO be over-engineering. Keep it simple. And 3 digits (for the axes only!) wouldn't hurt in flight, either. Oh well, just another minor detail to argue over ... ;-) m. ------------------------------------------------------------------------- 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
