20,741
edits
FlightGear Newsletter September 2012: Difference between revisions
Jump to navigation
Jump to search
m
FlightGear Newsletter September 2012 (view source)
Revision as of 00:46, 23 September 2012
, 23 September 2012→Canvas System: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38344.html
m (→Canvas System: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38344.html) |
|||
| Line 40: | Line 40: | ||
As a first proof of concept, Stuart has added a Canvas-based map to the airport selection dialog, and Hooray has demonstrated that the same technique could be used to add a map widget to the route manager dialog - so that airport selection and route planning could become more intuitive using the [[Canvas]] system. For additional info, please see: [http://flightgear.org/forums/viewtopic.php?f=71&t=17625]. | As a first proof of concept, Stuart has added a Canvas-based map to the airport selection dialog, and Hooray has demonstrated that the same technique could be used to add a map widget to the route manager dialog - so that airport selection and route planning could become more intuitive using the [[Canvas]] system. For additional info, please see: [http://flightgear.org/forums/viewtopic.php?f=71&t=17625]. | ||
In addition, ShivaVG (the vector drawing engine behind canvas) has been extended to support some kind of a non-zero fill rule. It's not really non-zero because instead of incrementing and decrementing depending on the orientation of the drawn overlapping regions it simply checks if at least a single region covers a pixel. For our use cases it | |||
should be enough tough. | |||
Some further performance improvements were added: Now the texture is only redrawn if something has changed. So if you don't change the map there shouldn't be any noticeable performance impact anymore. | |||
Also the bounding boxes are now only written to the property tree if they are recalculated. This should take some fair amount of changing properties away. | |||
Seems like now tessellating takes much longer than before due to the amount of data in one single path. | |||
The current problem with zooming is that every position of every path gets recalculated with the updated projection, even though this isn't really needed as the projection doesn't noticeably while just zooming | |||
and scrolling around at a single airport. | |||
=== Flightplan access via Scripting === | === Flightplan access via Scripting === | ||