20,741
edits
Canvas properties: Difference between revisions
Jump to navigation
Jump to search
→Planned Features
| Line 52: | Line 52: | ||
* [[#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) {{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 | * '''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."{{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" | * '''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." {{Not done}} | |||
=== Adressing modes: by-index, by-name (property mounting) === | === Adressing modes: by-index, by-name (property mounting) === | ||