20,741
edits
FlightGear Newsletter September 2012: Difference between revisions
Jump to navigation
Jump to search
FlightGear Newsletter September 2012 (view source)
Revision as of 17:51, 30 September 2012
, 30 September 2012→Canvas System
| Line 52: | Line 52: | ||
This approach would also make it possible to directly show instruments in GUI dialogs or vice versa. | This approach would also make it possible to directly show instruments in GUI dialogs or vice versa. | ||
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. A first stab at an MVC-oriented design to create map layers has now been committed to the base package, documented at [[Canvas Map API]] - this will soon be re-worked to add support for additional dialogs and instruments. | ||
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 | 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 | ||