Canvas properties: Difference between revisions

Canvas properties (view source)

634 bytes removed , 17 October 2013

m

20,741

edits

@@ Line 134: / Line 134: @@
 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 ===
-Looking at omega95's ATR72 code, it might make sense to extend the API such that it'll be possible to set up some defaults for all children, so that colors/fonts/size etc. can be set up once for a group, and so that they don't need to be specified manually each time, i.e. defaults are applied automatically if not specified otherwise
-: This is definitely something we'll need, also for supporting styling. I have currently something like (or a subset) of CSS in mind. We only need to take care that it stays performant even with a large number of elements, so this should be best implemented in C++.
 === Render 3D models to a texture ===