20,741
edits
Property browser: Difference between revisions
Jump to navigation
Jump to search
m
→Tied properties
mNo edit summary |
|||
| Line 14: | Line 14: | ||
== Tied properties == | == Tied properties == | ||
{{Note|The origin of tied properties was largely to address | |||
"hypothetical" performance concerns in the early days. Coders could | |||
continue to use native compiled variables and simultaneously expose them to | |||
the property system. Early property system skepticism included issues like | |||
performance and use of global structures. Those have largely not proven | |||
out to be actual issues. So without looking deep into how much | |||
effort/change/impact this would require, I think for the most part the | |||
whole tied property aspect of the api could go away and the property system | |||
api would simplify quite a bit.<ref>https://sourceforge.net/p/flightgear/mailman/message/37280934/</ref> | |||
}} | |||
Some properties are so called ''tied'' properties which are directly mapped to internal C++ variables and they cannot be modified using the property browser, we are currently trying to get rid of tied properties, see [[Howto:Use_Property_Tree_Objects]] for details. | Some properties are so called ''tied'' properties which are directly mapped to internal C++ variables and they cannot be modified using the property browser, we are currently trying to get rid of tied properties, see [[Howto:Use_Property_Tree_Objects]] for details. | ||