20,741
edits
Canvas properties: Difference between revisions
Jump to navigation
Jump to search
m
→Serializing a canvas to a buffer or file
m (→Nested/shared "multipass" Canvases: clean up & delete outdated stuff) |
|||
| Line 106: | Line 106: | ||
=== Serializing a canvas to a buffer or file === | === Serializing a canvas to a buffer or file === | ||
{{cquote|<nowiki>I am also thinking about some kind of one-time canvas, where the | |||
contents are just rendered once and afterwards can be used in an other | |||
canvas as a texture and maybe even stored on the hard disk an reused the | |||
next time FlightGear is started up.</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38354.html|title=<nowiki>Airport Selection feedback</nowiki>|author=<nowiki>Thomas Geymayer</nowiki>|date=<nowiki>22-09-2012</nowiki>}}</ref>|<nowiki>Thomas Geymayer</nowiki>}} | |||
<references/> | |||
See [[FGPlot#Feature_Requests]]: provide a new Nasal API to serialize a canvas texture (or group) to an osg::Image in $FG_HOME, so that graphs can be easily saved and shared/posted without users having to take full screen shots and then having to edit the image [http://flightgear.org/forums/viewtopic.php?f=49&t=17540&hilit=gnuplot#p166472] | See [[FGPlot#Feature_Requests]]: provide a new Nasal API to serialize a canvas texture (or group) to an osg::Image in $FG_HOME, so that graphs can be easily saved and shared/posted without users having to take full screen shots and then having to edit the image [http://flightgear.org/forums/viewtopic.php?f=49&t=17540&hilit=gnuplot#p166472] | ||