Canvas Maps: Difference between revisions

Jump to navigation Jump to search
823 bytes removed ,  15 July 2013
m
→‎Canvas Groups/Layers {{Done}}: clean up - delete stuff that's already been implemented for a while
m (Link to special directory articles)
m (→‎Canvas Groups/Layers {{Done}}: clean up - delete stuff that's already been implemented for a while)
Line 112: Line 112:
* http://flightgear.org/forums/viewtopic.php?f=71&t=17105&p=163120&hilit=synthetic#p163119
* http://flightgear.org/forums/viewtopic.php?f=71&t=17105&p=163120&hilit=synthetic#p163119
* http://flightgear.org/forums/viewtopic.php?f=71&p=164340#p163475
* http://flightgear.org/forums/viewtopic.php?f=71&p=164340#p163475
== Canvas Groups/Layers {{Done}} ==
The layer/grouping feature we talked about will definitely be useful once the canvas is being used for such displays, because these "layers" can usually be toggled individually - so group sorting to disable hierarchies of drawable nodes, sounds like the way to go.
Fortunately, with the canvas system, it will be possible to reuse the same code for GUI dialog widgets AND instruments, so there will be less duplicate code.
The only thing that's required for different aircraft or different dialogs is exposing some form of "style" helper, so that symbols/colors/fonts can be customized for different needs and instruments.
If that could be made to work, people could easily instantiate a new MFD gauge (or dialog!) and just customize it according to their needs, which will be great.


== Planned Features {{Pending}} ==
== Planned Features {{Pending}} ==

Navigation menu