> The following aircraft override the radio dialog, which has moved since
> v2.0.0.
>
> 777-200ER
> b1900d
> Citation-Bravo
>
> I've just pushed an enhancement to gui.nas that allows the aircraft developer
> to
> change the binding for a symbolically named dialog, in the same way
> that they can
> enable/disable dialogs and menus using the existing gui.menuEnable() function.
>
> So, you can now put the following code in your aircraft-specific Nasal files:
>
> gui.menuBind("radio", "dialogs.Radio.open()");
>
> This replaces the binding for the "radio" menu item with a command to open the
> dialogs.Radio dialog box (that you've defined elsewhere).
>
>
> Syd - I think all these aircraft are yours. Could you update them to
> use the new function?
>
> Hint: - the code you want for the 777-200ER is to add the following
> to the bottom of
> 777-200ER/Nasal/dialogs.nas:
>
> gui.menuBind("radio", "dialogs.Radio.open()");
> gui.menuBind("autopilot-settings", "dialogs.ap_settings.open()");
>
> -Stuart
Sounds like a much easier solution , thanks . I can fix all these
tomorrow ... still not sure how to go about commiting them though ....
maybe I'll reread git for dummies ;)
Syd
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
