Canvas properties: Difference between revisions

Jump to navigation Jump to search
m
m (→‎Vector Data Cache: obsolete IMO)
Line 124: Line 124:


Another use-case would be screen shots of individual dialogs, currently users need to capture the whole screen and then cut out the relevant part (see [https://code.google.com/p/flightgear-bugs/issues/detail?id=1192]) - it would be awesome if we could have some dedicated API to capture a canvas and write it to a file, so that only relevant stuff ends up in the file, rather than the whole screen.
Another use-case would be screen shots of individual dialogs, currently users need to capture the whole screen and then cut out the relevant part (see [https://code.google.com/p/flightgear-bugs/issues/detail?id=1192]) - it would be awesome if we could have some dedicated API to capture a canvas and write it to a file, so that only relevant stuff ends up in the file, rather than the whole screen.
=== Render 3D models to a texture ===
Omega95 mentioned how being able to load a 3D model and transform/render it to a 2D texture would allow more complex instruments and GUI widgets to be implemented using the Canvas system. This should probably be added as a custom canvas "mode", and it should probably be implemented such that it may later on be extended to also support scenery views using CompositeViewer or FlightGear aircraft [http://forum.flightgear.org/viewtopic.php?f=4&p=164245#p164243]. {{Not done}}


=== Smart Labels for OSGText elements ===
=== Smart Labels for OSGText elements ===

Navigation menu