Currently GTlab is very sensitive on the order of how properties and subproperties are registered. If done wrong, the signals from subproperties won't be escalated.
In particular if a property is registered first and then a subproperty is registered, the changed signal of the subproperty won't be escalated to the GTObject.
We should change this behaviour in GTlab 2.1
Related to issue #1126
Impact on the codebase
Ideally, only on GTObject and GTAbstractProperty. Still, there is a risk, that too many properties could be suddenly created, leading to strange effects on the GUI side.
Current workarounds
The order of registration needs to be done in the correct oder. 1. subprops, 2. props.
Summary
Currently GTlab is very sensitive on the order of how properties and subproperties are registered. If done wrong, the signals from subproperties won't be escalated.
In particular if a property is registered first and then a subproperty is registered, the changed signal of the subproperty won't be escalated to the GTObject.
We should change this behaviour in GTlab 2.1
Related to issue #1126
Impact on the codebase
Ideally, only on GTObject and GTAbstractProperty. Still, there is a risk, that too many properties could be suddenly created, leading to strange effects on the GUI side.
Current workarounds
The order of registration needs to be done in the correct oder. 1. subprops, 2. props.