[Flightgear-devel] Re: [PATCH] GUI/menubar.[ch]xx, Main/fg_commands.cxx: add fgCommand to disable/enable menu entries
* Melchior FRANZ -- Tuesday 06 December 2005 15:20: the attached patch adds an fgCommand that allows to disable/enable menu entries This should better be hooked into the property tree, so that one can directly set /sim/menubar/default/menu[2]/item[3]/enabled to false and get the menu disabled. Working on that. Comments still welcomed, though. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: [PATCH] GUI/menubar.[ch]xx, Main/fg_commands.cxx: add fgCommand to disable/enable menu entries
This should better be hooked into the property tree, so that one can directly set /sim/menubar/default/menu[2]/item[3]/enabled to false and get the menu disabled. Working on that. Comments still welcomed, though. Great idea. Do that, and I'll rework the CH Products Yoke cyclic hack to add a menu that would allow to disable the cyclic control from the yoke if /rotors is detected. Moreover, thereafter the thing will remove itself from the menu :-) V ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: [PATCH] GUI/menubar.[ch]xx, Main/fg_commands.cxx: add fgCommand to disable/enable menu entries
Melchior FRANZ wrote: * Melchior FRANZ -- Tuesday 06 December 2005 15:20: the attached patch adds an fgCommand that allows to disable/enable menu entries This should better be hooked into the property tree, so that one can directly set /sim/menubar/default/menu[2]/item[3]/enabled to false and get the menu disabled. Working on that. Comments still welcomed, though. And I still believe, that you should not have to set this to false, but set it to true if you want that item enabled. If this is done in the general autopilot config it's automatically done for all it's users, so there's no change. But the semantics would look right (at least to me), because the autopilot should define what dialog it shows/supports. Even if custom autopilot dialogs are not supported yet. Nine ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
