omega95 wrote:
if we had a vertical WPT and hard-coded terrain layer (this is tricky as it's dependent on the WPTs) this almost exactly be like the ND.
For starters, I think these are the main steps to port your work to become a MapStructure layer
- extend api.nas to allow "vertical" maps to be added, these would be just canvas groups for now, because we don't have support for hard-coded projections currently
- i.e. change the .addLayer() method to add a mandatory mode/projection argument (defaulted to "horizontal")
- support a *.symbol field that also defaults to "horizontal", but which can be overridden by vertical layers
- add a new MapStructure layer that renders a polygon, the lcontroller file would then simply return a set of lat/lon/alt vertices
- investigate if/how to reuse lcontroller files (WPT/RTE)
Overall, this shouldn't be very difficult, and it would allow omega95's work to be reused in other places, including other aircraft and GUI dialogs.
At the same time, this would mean that we'd support independent instances and styling, too.