20,741
edits
(→2017) |
|||
| Line 6: | Line 6: | ||
== 2017 == | == 2017 == | ||
=== Groups and Colors === | |||
Thorsten learned something rather important about canvas: After doing canvas a while, most of us love the concept to suitably group things and then translate or hide the whole group, which is a very performance-friendly way to get the job done compared with moving all elements. | |||
Thorsten had the situation that the Shuttle HUD has several de-clutter levels which are progressively hidden as the de-clutter function is used. So, he introduced dc0 to dc3 as the groups and operate with selective setVisible() on them according to chosen de-clutter level. | |||
Doing brightness adjustment of the HUD by setting color on the group (specifically the alpha channel). | |||
Unlike translations, rotations or visible statements acting on the top level of the group, this one seems to be passed recursively down the child elements, leading to a huge property I/O. | |||
Anyway, if you know what it does, it's a very useful function still - just it can't be used in a performance-critical place, and it should not be confused with performance-friendly group operations.<ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=307073#p307073 | |||
|title = <nowiki> Color and groups - beware! </nowiki> | |||
|author = <nowiki> Thorsten </nowiki> | |||
|date = Mar 16th, 2017 | |||
|added = Mar 16th, 2017 | |||
|script_version = 0.40 | |||
}}</ref> | |||
=== Canvas GUI === | === Canvas GUI === | ||
James is planning a bit of work in the Canvas GUI/widgets area but in the medium term (mid 2017), he wouldn't recommend making lots of extensions to the current Canvas GUI toolkit because he wants to give the whole Canvas-GUI architecture a review and sanity-check first. For the time being, he has no idea if this will be compatible or incompatible with the existing GUI controls, or even be successful. <ref>{{cite web | James is planning a bit of work in the Canvas GUI/widgets area but in the medium term (mid 2017), he wouldn't recommend making lots of extensions to the current Canvas GUI toolkit because he wants to give the whole Canvas-GUI architecture a review and sanity-check first. For the time being, he has no idea if this will be compatible or incompatible with the existing GUI controls, or even be successful. <ref>{{cite web | ||