2,733
edits
Howto:Prototyping a new NavDisplay Style: Difference between revisions
Jump to navigation
Jump to search
m
Howto:Prototyping a new NavDisplay Style (view source)
Revision as of 15:41, 16 November 2016
, 16 November 2016Update {{func link}} form
Red Leader (talk | contribs) m (Update {{func link}} form) |
|||
| Line 116: | Line 116: | ||
* add tooltips, and mouseover events for ND elements - e.g. name of the layer/symbol etc ? | * add tooltips, and mouseover events for ND elements - e.g. name of the layer/symbol etc ? | ||
* add a mode to close the dialog and decouple the ND (no PUI overhead) ? | * add a mode to close the dialog and decouple the ND (no PUI overhead) ? | ||
* Use {{Func link|bind}} to make io.include work within {{Func link|call}} | * Use {{Func link|bind()}} to make io.include work within {{Func link|call()}} | ||
* Consider supporting an actual texture map (use one of the aircraft textures) to show a proper MCP instead of those checkboxes (ask Hyde/Gijs) ? | * Consider supporting an actual texture map (use one of the aircraft textures) to show a proper MCP instead of those checkboxes (ask Hyde/Gijs) ? | ||
* Use an outer/embedded Canvas for the UI ? (see the Garmin 196) <ref>https://forum.flightgear.org/viewtopic.php?f=4&p=297433#p297424</ref> | * Use an outer/embedded Canvas for the UI ? (see the Garmin 196) <ref>https://forum.flightgear.org/viewtopic.php?f=4&p=297433#p297424</ref> | ||