@TheTom: Patch at: Subject: How to display Airport Chart?
Getting this reviewed/committed in time for 3.2 would be useful for 1) porting the map dialog, 2) tutorials/missions:
Subject: How to display Airport Chart?
Hooray wrote:zakalawe wrote in Sat Nov 09, 2013 2:51 am:Looking good, can you get this working so we can replace the map-widget for 3.0?
We need to check what's missing, or rather, what would be useful to replace the map widget completely/properly. For example, as far as I know, we don't currently have any hooks into the replay/flight recorder subsystem, which is however what's used to show flight path history,right ? So the poor-man's approach would be using a timer and sampling the position separately, but having access to the replay/recorder system would be great for many other reasons, so exposing it via cppbind would be awesome.
Subject: NavDisplay & MapStructure discussion (previously via PM)
Hooray wrote:right, history would be kind of a hack ATM, but I can ask Tom to review & commit the patch that I came up with a while ago - otherwise, we would need to register a timer that samples things like lat/lon/alt without being tied to MapStructure
Subject: Tutorials/Missions/Adventures: requests for features
Hooray wrote:anything related to piloting/aerobotatics (red bull air race) and maneuvers will require some means to do flight profile tracking, either by sampling lat/lon/alt or by hooking into the replay/history subsystems (currently not exposed to Nasal).
PS: It would also be good if the project/unproject hooks discussed in Issue 550 could be exposed, so that we can better support panning & projections (unless you have a better idea here) - performance-wise it would be great if we could beat the performance of the built-in ND, e.g. by using a pre-created lat/lon grid, stored as a raster image and referenced/transformed via a separate group. Philosopher also mentioned that he'd prefer using native Canvas windows for the new map, for which we'd only need 2-3 additional widgets (actually checkboxes should do for now), so that the whole thing could be procedurally instantiated, without requiring any PUI/XML stuff.