Closed KAINLabs closed 3 months ago
Hi @KAINLabs
Thanks for reporting, just 'fixed' it, but changes don't show up in the designer. Any thoughts @Smurf-IV?
but changes don't show up in the designer. Any thoughts @Smurf-IV?
You have to add an attribute so that the designer forces a refersh of the displayed control when the value changes.
but changes don't show up in the designer. Any thoughts @Smurf-IV?
You have to add an attribute so that the designer forces a refersh of the displayed control when the value changes.
RefreshProperties
attribute?
RefreshProperties attribute?
Yes that's appears to be the one I was thinking about..
And / Or checking if InDesignerMode
and calling Refresh()
to perform a designer invalidate.
Fixes may need to be applied to all controls.
Hmm... I don't understand why this won't work?
/// <inheritdoc />
[RefreshProperties(RefreshProperties.Repaint)]
public new bool Enabled
{
get => base.Enabled;
set
{
base.Enabled = value;
if (DesignMode)
{
Refresh();
}
}
}
@Wagnerp re: The commit referenced above; What did it do for this bug ?
Because you started down the designer route, when the Original was at runtime ?
@Wagnerp re: The commit referenced above; What did it do for this bug ?
Because you started down the designer route, when the Original was at runtime ?
@Smurf-IV Nothing, works at runtime but not in the designer. But I think this is standard WinForms practice.
@Wagnerp
Is this one still on or cant it be closed, since Smurf added the wont fix label?
@Wagnerp
Is this one still on or cant it be closed, since Smurf added the wont fix label?
@giduac
Works at runtime, but not in the designer, just like any other WinForm control. So I'd say yes.
When changing the Enabled property from false to true, the color style remains disabled and the control cannot be interacted with, even though the property says it is set to true/enabled.
To Reproduce Steps to reproduce the behavior:
Expected behavior The visual color scheme should change to active/enabled and the user should be able to interact with it.
Desktop
Additional context Looking at the source code for the KryptonComboBox, this issue may have something to do with there being 2 OnEnabledChanged override events in the control. The newer one has comments about not forwarding the event as a fix for issue 662.