[Flightgear-devel] Re: Flightgear-devel Digest, Vol 32, Issue 19

[Steve Knoblock]

On Tue, 06 Dec 2005 12:00:24 -0600, you 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.

m.

This is excellent. Yes, please do. This will at least open up access
to the menu system and let the various developers of aircraft and
menus make the choice of how to interact with the menu.

My only caution would be possible malicious disabling of essential
menus. I think the author would be exposed pretty quickly, so the
benefit outweighs the risk. I suppose one could do the same with
Firefox...

-sek



___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

[Flightgear-devel] Re: Flightgear-devel Digest, Vol 32, Issue 19

[Melchior FRANZ]

* Steve Knoblock -- Tuesday 06 December 2005 21:16:
 My only caution would be possible malicious disabling of essential
 menus. I think the author would be exposed pretty quickly,

Exactly. And this isn't the first opportunity for aircraft designers
to annoy others. What about a Nasal script that endlessly creates 
property nodes? Or disables mouse, keyboard and joystick? What about
making a really bad FDM config? Sounds familiar? We have some of
those already!  ;-)  Seriously, this is a non-issue. Code that goes
into cvs is reviewed and quickly fixed. And if something doesn't
work as expected, you erase it from your disk. Viola.

m.

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d