20,741
edits
Canvas tile element: Difference between revisions
Jump to navigation
Jump to search
m
https://www.mail-archive.com/flightgear-devel@flightgear.org/msg30262.html
m (https://www.mail-archive.com/flightgear-devel@flightgear.org/msg16345.html) |
m (https://www.mail-archive.com/flightgear-devel@flightgear.org/msg30262.html) |
||
| Line 8: | Line 8: | ||
The nice thing about Atlas is that it uses the current FlightGear scenery for generating it's maps. If we get better scenery, Atlast produces better maps.<ref>https://www.mail-archive.com/flightgear-devel@flightgear.org/msg16345.html</ref> | The nice thing about Atlas is that it uses the current FlightGear scenery for generating it's maps. If we get better scenery, Atlast produces better maps.<ref>https://www.mail-archive.com/flightgear-devel@flightgear.org/msg16345.html</ref> | ||
This issue of not being able to render maps to a sub window is coming back to bite us every time. If it's not stuff like this then it's moving map/GPS/ND type instruments. <ref>https://www.mail-archive.com/flightgear-devel@flightgear.org/msg30262.html</ref> | |||
James originally implemented the a moving navigational [[Map]] as a custom PUI widget - it's *not* an Atlas-replacement, or an MPMap replacement, i.e. not intended to also display terrain elevation <ref>https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg27097.html</ref> | James originally implemented the a moving navigational [[Map]] as a custom PUI widget - it's *not* an Atlas-replacement, or an MPMap replacement, i.e. not intended to also display terrain elevation <ref>https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg27097.html</ref> | ||