1. Nothing. It is simply a convention to make it clear to the user that these properties are not part of the public API and should not be used in third party software.
2. In principle yes. But there are no guarantees that those properties will exist in a future Qt release or keep the same behaviour. If you make use of those properties, your code might stop working with a future Qt release.
3. Not really. More recent versions of Qt Creator might hide them from code completion or code browsing and qdoc will skip those properties while generating documentation. Aside from that they are just regular properties.
4. It doesn’t. We were discussing the possibility of introducing private property scopes at the Qt Contributors Summit this week but there are currently no concrete plans. Regardless, just like in C++, we will always need to declare some public functions that we want to keep outside of the public API.
↧