20,741
edits
Canvas tile element: Difference between revisions
Jump to navigation
Jump to search
no edit summary
m (https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg33880.html) |
No edit summary |
||
| Line 1: | Line 1: | ||
{{Stub}} | {{Stub}} | ||
[[File:Atlas.jpg|thumb|270px|Atlas map view of the San Francisco bay area]] | |||
Some contributors have been experimenting with atlas based moving map displays (with pre-rendered Atlas images), but with nasal code.<ref>https://sourceforge.net/p/flightgear/mailman/message/20010870/</ref> <ref>https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg33880.html</ref> | Some contributors have been experimenting with atlas based moving map displays (with pre-rendered Atlas images), but with nasal code.<ref>https://sourceforge.net/p/flightgear/mailman/message/20010870/</ref> <ref>https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg33880.html</ref> | ||
| Line 59: | Line 62: | ||
== Idea == | == Idea == | ||
{{Main article|Atlas}} | {{Main article|Atlas}} | ||
Given that we do have existing code to render such maps, and that the Canvas system does have support for loading raster images ([[Canvas Image|sc::Image]]), this would be the most straightforward option to ensure that there is no mismatch between a moving map and a corresponding radar display, because it'd be using the same underlying terrain/vector data. | Given that we do have existing code to render such maps, and that the Canvas system does have support for loading raster images ([[Canvas Image|sc::Image]]), this would be the most straightforward option to ensure that there is no mismatch between a moving map and a corresponding radar display, because it'd be using the same underlying terrain/vector data. | ||