FlightGear Newsletter October 2016: Difference between revisions

m
→‎A standalone Canvas NavDisplay Dialog: lol, that's the most awesome typo I've seen in a long time
m (→‎A standalone Canvas NavDisplay Dialog: lol, that's the most awesome typo I've seen in a long time)
Line 85: Line 85:
[[File:ND-Airbus-Style-With-Route.png|thumb|Screenshot showing Gijs' [[NavDisplay]] using the Airbus style created by artix in a [[PUI]] dialog with an embedded [[Canvas]] widget to render the ND and the corresponding widgets.]]
[[File:ND-Airbus-Style-With-Route.png|thumb|Screenshot showing Gijs' [[NavDisplay]] using the Airbus style created by artix in a [[PUI]] dialog with an embedded [[Canvas]] widget to render the ND and the corresponding widgets.]]


In the last couple of days, we have created a new dialog that can be used to easily prototype new [[NavDisplay]] styles, showing multiple ND instances for each pilot, which can be controlled/tested independently (using different settings for range, modes, traffic etc). Once the dialog is closed/reopened, the underlying navdisplay.mfd/styles files are also automatically reloaded from disk, so that you don't need to exist/restart fgfs to test your changes.
In the last couple of days, we have created a new dialog that can be used to easily prototype new [[NavDisplay]] styles, showing multiple ND instances for each pilot, which can be controlled/tested independently (using different settings for range, modes, traffic etc). Once the dialog is closed/reopened, the underlying navdisplay.mfd/styles files are also automatically reloaded from disk, so that you don't need to exit/restart fgfs to test your changes.


Under the hood, this is a conventoinal PUI/XML dialog with multiple embedded CanvasWidget areas that instantiate independent ND instances using a subset of the code commonly found in the aircraft specific ND.nas file, adapted to use the embedded Canvas region for rendering multiple NDs and GUI buttons/widgets added to control the whole thing without necessarily requiring a fully developed cockpit.
Under the hood, this is a conventoinal PUI/XML dialog with multiple embedded CanvasWidget areas that instantiate independent ND instances using a subset of the code commonly found in the aircraft specific ND.nas file, adapted to use the embedded Canvas region for rendering multiple NDs and GUI buttons/widgets added to control the whole thing without necessarily requiring a fully developed cockpit.