Canvas properties: Difference between revisions

Jump to navigation Jump to search
Line 49: Line 49:
* Support drawing to GUI widgets {{Done}}  
* Support drawing to GUI widgets {{Done}}  
* 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. {{Not 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) {{Not 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) {{Not done}}
* '''TheTom''': "If each widget/tool/whatever don't creates an own canvas, but instead just attaches itself to a given group infinite nesting of "canases" would be easily possible already with the current implementation. 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." {{Not done}}
* '''TheTom''': "If each widget/tool/whatever don't creates an own canvas, but instead just attaches itself to a given group infinite nesting of "canases" would be easily possible already with the current implementation. 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." {{Not done}}

Navigation menu