Canvas MapStructure: Difference between revisions

Canvas MapStructure (view source)

61 bytes removed , 11 April 2016

Now in FlightGear

2,733

edits

@@ Line 1: / Line 1: @@
-{{Template:Non-stable|version=3.2|progress=80}}
 {{infobox subsystem
 |image =MapStructureDialog.png
@@ Line 21: / Line 18: @@
 [[File:MapStructure-WXR-layer-by-omega95.png|thumb|MapStructure WXR (weather) layer created by omega95's using a web service API to fetch live online imagery[http://forum.flightgear.org/viewtopic.php?f=71&t=23753]]]
-{{Template:Canvas Navigation}}
+{{Canvas Navigation}}
 '''Targeted FlightGear versions: 3.20+'''
@@ Line 119: / Line 115: @@
 At the moment, the primary users of the framework are the 747-400 and the 777-200ER - both make use of the new [[NavDisplay|ND framework]], which internally uses the MapStructure framework.
-If you just need  an ND, you won't need to deal with MapStructure directly, it is all done transparently by the [[NavDisplay]] code.
+If you just need an ND, you won't need to deal with MapStructure directly, it is all done transparently by the [[NavDisplay]] code.
 However, if you'd like  to create custom charting displays, or GUI dialogs with embedded charts (map dialog, instructor console, ATC or RADAR displays etc), you'll probably want to use the MapStructure framework, because it reduces the amount of specialized Nasal code significantly - typically to ~10-15 lines of configuration code per layer.