-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: KryptonRibbonGroup Controls remain enabled at runtime when set to disabled in the designer. #1561
Comments
@giduac I also found the disabling missing in the following controls:
|
@Wagnerp As so many controls have this missing, then I am assuming it is not a regression, OR, the timing of events is now different in the later core nets compared with framework ! |
…`Enabled` and `Visible` states #1561
@Smurf-IV Anyways best to pull them all up to the same level... |
Describe the bug
KryptonRibbonGroup Controls remain enabled at runtime when set to disabled in the designer.
Controls affected:
To Reproduce
Steps to reproduce the behavior:
Enabled
property tofalse
Expected behaviour
When the control first is created and set to disabled it is still accessible.
If at runtime the control is set to disabled or enabled the control responds correct.
So at initialization the inner control is not disabled while the outer control is.
Screenshots
Show the setting after the property has been set the first time through the designer source.
devenv_6Zd4bXVkUg.mp4
Desktop (please complete the following information):
Additional Info
Other controls that don't have this problem have a similar codebase.
On first run when the control is set to disabled the propertyhandler has no subscribers. Tested that on TextBox and ComboBox. Though ComboBox does work.
Happens in both Ribbon Triple and Line Group.
Work-around
After
InitializeComponent()
has run, disabled controls from code.Handle it from the property itself:
The text was updated successfully, but these errors were encountered: