6,566
edits
Canvas properties: Difference between revisions
Jump to navigation
Jump to search
Switch to {{flightgear source}} and {{flightgear url}} to fix the broken Gitorious links.
(Switch to {{flightgear source}} and {{flightgear url}} to fix the broken Gitorious links.) |
|||
| Line 20: | Line 20: | ||
=== Try it out === | === Try it out === | ||
The latest information on the canvas subsystem can be found in | The latest information on the canvas subsystem can be found in {{flightgear source|path=docs-mini/README.canvas|text=README.canvas}}. | ||
[[File:Cessna 172P Canvas Demo.png|380px|thumb|Demonstration of the new Canvas drawing API on the Cessna 172P.]] | [[File:Cessna 172P Canvas Demo.png|380px|thumb|Demonstration of the new Canvas drawing API on the Cessna 172P.]] | ||
| Line 37: | Line 37: | ||
== ChangeLog == | == ChangeLog == | ||
* Support a Scenery Placement mode {{done}} (WIP: [ | * Support a Scenery Placement mode {{done}} (WIP: [{{flightgear url|commit=eba03b5e469824ee8f1494723fcddbbc56155a08|view=commit}}]) | ||
* Support drawing to textures for aircraft instruments {{Done}} | * Support drawing to textures for aircraft instruments {{Done}} | ||
* Support drawing to aircraft HUDs {{Done}} | * Support drawing to aircraft HUDs {{Done}} | ||
| Line 47: | Line 47: | ||
* Support implementing GUI widgets using Canvas/Nasal {{Pending}} (see [[Canvas Widgets]]) | * Support implementing GUI widgets using Canvas/Nasal {{Pending}} (see [[Canvas Widgets]]) | ||
* [[#Images: Static Textures & Cascaded Canvases|Static image files]]: should be handled like any other element on the canvas. Only instead of specifying a path you'll have to set the file system path to an image which will be loaded with osg. {{Done}} | * [[#Images: Static Textures & Cascaded Canvases|Static image files]]: should be handled like any other element on the canvas. Only instead of specifying a path you'll have to set the file system path to an image which will be loaded with osg. {{Done}} | ||
* Support placing canvas textures into the scenery, so that dynamic scenery features (i.e. a [http://en.wikipedia.org/wiki/Visual_Docking_Guidance_System visual docking guidance system] or runway skid marks) can be implemented using the canvas system (being discussed and planned as of 08/2012) {{Done}} [ | * Support placing canvas textures into the scenery, so that dynamic scenery features (i.e. a [http://en.wikipedia.org/wiki/Visual_Docking_Guidance_System visual docking guidance system] or runway skid marks) can be implemented using the canvas system (being discussed and planned as of 08/2012) {{Done}} [{{flightgear url|commit=eba03b5e469824ee8f1494723fcddbbc56155a08|view=commit}}] (WIP) | ||
* '''Hooray''': "yes, sounds like the best and most powerful design to me, because everything would still be a canvas, but nesting/recursion would be supported, i.e. "piping" the output from one canvas into another canvas group, so that canvases can be reused and nested" {{Done}} | * '''Hooray''': "yes, sounds like the best and most powerful design to me, because everything would still be a canvas, but nesting/recursion would be supported, i.e. "piping" the output from one canvas into another canvas group, so that canvases can be reused and nested" {{Done}} | ||
* '''TheTom''': "Maybe I should add means to define clipping regions to guarantee widgets can't draw outside their assigned regions, i.e. perform clipping only if there is actually a clipping region specified." {{Done}} | * '''TheTom''': "Maybe I should add means to define clipping regions to guarantee widgets can't draw outside their assigned regions, i.e. perform clipping only if there is actually a clipping region specified." {{Done}} | ||