StyleDemo2.zip (104.8 KB)
I comeback to you regarding point 3 which can be reproduced in the last version.
Please find attached new demo sources.
In the main form, you will find 4 identical TAdvSpinEdit components. Only the enable property change. You can edit the enable property at runtime with chekboxes. The application use the "light" vcl style.
The four TAdvSpinEdit have four different behaviours:
1- AdvSpinEdit is disabled in the designer. During runtime time, you can enable/disable, buttons always remain grey.
2- AdvSpinEdit is enabled in the designer. During runtime time, you can enable/disable, buttons always respect the style.
3- AdvSpinEdit is enabled in the designer but disabled in form create. During runtime, you can enable/disable, buttons remain grey. Then enable AdvSpinEdit and move the cursor on buttons to highlight them. They get the right style. Then you can enable/disable, buttons now always respect the style.
4- AdvSpinEdit is enabled in the designer but disabled in form create. Here when clicking on checkbox, component is hidden then enabled/disabled then shown again. During runtime time, when the component is disabled buttons are grey, and when the component are enabled buttons have the right style.
In our main application we have this kind of issue. Disabled TAdvSpinEdit have grey buttons. After enabling and highlighting, somtimes they get the right style, sometimes not. After disabling, sometimes they revert to grey sometimes not. It depends on the component according to the way to update the visibility and the availability. Unfortunately, the grey buttons make our user interface not very nice.