Thank you for your explanation. It's clear now
As for the Settings Panel, some people like it and some people don't. But looking back, I would make it like a regular properties panel instead of the fancy kind like it is now. It would be simpler to code and load up faster.
Yes, these are important points. Please remember about few others:
When people decide to draw own sets of components they should really remember about common features. Users expect some behaviour from control even if it looks different. If they assume that something is a button, it should behave like it.
As an example: In few places of Orbit Settings dialog there are links for toggling between different settings groups. Nobody expects that clicking on them will hide previous group and reveal another one instead.
Even if you painted furniture, you will never expect that putting your head on the pillow will switch your oven on
Another thing is the layout (alignments) and controls sizes (automatic Width at least). Having static parameters produces some problems for translators. Even if the application look right for the author's language it might be visually broken for others. In many cases language files are full of strange abbreviations there is because of that. It should be avoided.
Personally I prefere to use standard controls for options because it makes main application better. Most of the users will see dock only so the time spent on it should be longer than for Settings dialog. Users go to this window pretty rarely and if that's happen they expect it to work as flawless as something they already saw. They don't expect bells and whistles but stability and simplicity. In many cases they just want to "go, set and leave as soon as it possible". No need for wondering "is it a link or button".
Thank you for reading my complains