A while ago, I suggested to introduce an optional options hash, where things like the radio (dme/nav) source could be specified for each instance.
I think the canvas-radar branch should have the corresponding for this.
Hooray wrote in Tue Mar 25, 2014 11:32 pm:I think the canvas-radar branch should have the corresponding for this.
positioned searches are always around the aircraft, when they should be around the Map area.
# FIXME: all of these positioned queries ignore the map's position
Nasal runtime error: Cannot stat file: /home/hyde/work/FlightGear/canvas-hackers-fgdata/Nasal/canvas/map/APS.lcontroller
at /home/hyde/work/FlightGear/canvas-hackers-fgdata/Nasal/io.nas, line 4
called from: /home/hyde/work/FlightGear/canvas-hackers-fgdata/Nasal/canvas/MapStructure.nas, line 604
called from: /home/hyde/work/FlightGear/canvas-hackers-fgdata/Nasal/canvas/MapStructure.nas, line 677
called from: /home/hyde/work/FlightGear/canvas-hackers-fgdata/Nasal/canvas/MapStructure.nas, line 684
called from: /home/hyde/work/FlightGear/canvas-hackers-fgdata/Nasal/canvas/MapStructure.nas, line 595
called from: /home/hyde/work/FlightGear/canvas-hackers-fgdata/Nasal/globals.nas, line 110
Philosopher wrote in Thu Apr 10, 2014 10:09 pm:I think weather/storms, airports, and routes are the only layers left
and we've proved they aren't too difficult to do. And I did get the disabled ones removed, with the exception of the aircraft symbol one. Certainly the next thing to do is to port the map, and I probably wouldn't remove the old one for a while. Performance is pretty good so far, and it's really only the TFC that needs to keep updating every frame - the others are usually good for minutes at a time.
I do need to check if we simply aren't using an available API functionality to change the start position of those searches, and if so, it's a really simple change because the map already exposes its position. Traffic does its own search, so it already works properly .
Users browsing this forum: No registered users and 3 guests