20,741
edits
Howto:Prototyping a new NavDisplay Style: Difference between revisions
Jump to navigation
Jump to search
Howto:Prototyping a new NavDisplay Style (view source)
Revision as of 15:16, 16 October 2016
, 16 October 2016→Base Package changes
m (→Code: should suffice for now) |
|||
| Line 43: | Line 43: | ||
{{Note|The following patch contains changes that mainly take care of two things: | {{Note|The following patch contains changes that mainly take care of two things: | ||
* properly referencing the <code>canvas</code> namespace, so that the ND module can be separately included via <code>io.include()</code> | * properly referencing the <code>canvas</code> namespace, so that the ND module can be separately included via <code>io.include()</code> | ||
* moving the initialization of aircraft specific SVG elements into the <code>navdisplay.styles</code> file, and the corresponding Boeing/Airbus entries there (see <code>initialize_elements()</code>) | * moving the initialization of aircraft specific SVG elements into the <code>navdisplay.styles</code> file, and the corresponding Boeing/Airbus entries there (see <code>initialize_elements()</code> | ||
As of 10/2016, these should be included of the base package, i.e. available in 2016.4 <ref>https://sourceforge.net/p/flightgear/fgdata/ci/109e4524247c535026b8ebaa4e1dbb10e010a5ce/</ref>) | |||
}} | }} | ||
<syntaxhighlight lang="diff">diff --git a/Nasal/canvas/api.nas b/Nasal/canvas/api.nas | <syntaxhighlight lang="diff">diff --git a/Nasal/canvas/api.nas b/Nasal/canvas/api.nas | ||