20,741
edits
Canvas properties: Difference between revisions
Jump to navigation
Jump to search
m
→Serializing a canvas to a buffer or file: https://code.google.com/p/flightgear-bugs/issues/detail?id=1192
m (→Status 05/2013) |
m (→Serializing a canvas to a buffer or file: https://code.google.com/p/flightgear-bugs/issues/detail?id=1192) |
||
| Line 130: | Line 130: | ||
In addition, being able to serialize canvases to files on disk, would also help us keeping our docs (the manual) more up to date, because our GUI being canvas-driven, screen shots could be created in an automated/scripted fashion, so that the LaTex docs could automatically show the latest GUI dialogs. | In addition, being able to serialize canvases to files on disk, would also help us keeping our docs (the manual) more up to date, because our GUI being canvas-driven, screen shots could be created in an automated/scripted fashion, so that the LaTex docs could automatically show the latest GUI dialogs. | ||
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. | |||
=== Element/Group Defaults === | === Element/Group Defaults === | ||