FlightGear Newsletter October 2016: Difference between revisions

Jump to navigation Jump to search

FlightGear Newsletter October 2016 (view source)

Revision as of 11:18, 4 November 2016

1,230 bytes removed ,  4 November 2016
→‎A standalone Canvas NavDisplay Dialog: Cleanup section
mNo edit summary
Line 55: Line 55:


=== A standalone Canvas NavDisplay Dialog ===  
=== A standalone Canvas NavDisplay Dialog ===  
[[File:ND-dialog-customizable-size-and-instances.png|left|thumb|Screenshot showing a [[PUI]] dialog with two [[NavDisplay]] instances, featuring support for customizable resolution/size of the ND as well as selectable number of NDs to be shown.]]
[[File:ND-dialog-customizable-size-and-instances.png|thumb|Screenshot showing the dialog with two independent NavDisplay instances]]
[[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 exit/restart fgfs to test your changes.
Hooray has been working on a dialog to easily prototype new [[NavDisplay]] styles. It is capable of showing multiple NavDisplay instances, which can be controlled and tested independently (using different settings for range, modes, traffic, etc.). The dialog will also reload the styles file (navdisplay.mfd) when it is reopened, meaning that FlightGear doesn't have to be restarted every time changes are made.


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.
As of 10/2016, this is pending review by Gijs and Hyde before it can be committed to the base package.


Thus, this is also a great tool for people flying aircraft that may not even have access to n ND.
''Continue reading at [[Howto:Prototyping a new NavDisplay Style]]…''
 
Obviously, this is particularly useful for rapid prototyping ("RAD"), i.e. quickly testing additions and changes without having to exit/restart fgfs and without having a full aircraft developed yet.
 
[[File:Canvas-nd-menubar-entry.png|thumb|Screenshot showing  [[PUI]] menubar with added '''Canvas NavDisplay''' entry for the Canvas ND dialog.]]
 
 
This is currently pending review by Gijs and Hyde before it can be committed to the  base package.
 
Continue reading at [[Howto:Prototyping a new NavDisplay Style]]...


=== Benchmarking Canvas Path Performance ===
=== Benchmarking Canvas Path Performance ===
Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/105646"

Navigation menu