You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
is there a way to bind SplitButton.IsEnabled to the command.canExecute?
My goal is to disable the SplitButton completly if the button command cannot be executed.
I think if the internal ToggleButton would have a TwoWay-Binding for IsButtonEnabled it might work delegating IsButtonEnabled in the SplitButtonsStyle: <fluent:SplitButton.Style> <Style TargetType="fluent:SplitButton"> <Style.Triggers> <Trigger Property="IsButtonEnabled" Value="False"> <Setter Property="IsEnabled" Value="False"/> </Trigger> </Style.Triggers> </Style> </fluent:SplitButton.Style>
But I don't know if that would have any side effects, and I'm not sure if I'm overlooking something really simple to achieve this behavior, hence the question.
Related: #467 (This behavior was once integrated as default but got reverted) #720
Environment
Fluent.Ribbon v7.0.0-alpha0661
Windows 10
.NET Framework 4.6.2
The text was updated successfully, but these errors were encountered:
Hi,
is there a way to bind SplitButton.IsEnabled to the command.canExecute?
My goal is to disable the SplitButton completly if the button command cannot be executed.
I think if the internal ToggleButton would have a TwoWay-Binding for IsButtonEnabled it might work delegating IsButtonEnabled in the SplitButtonsStyle:
<fluent:SplitButton.Style>
<Style TargetType="fluent:SplitButton">
<Style.Triggers>
<Trigger Property="IsButtonEnabled" Value="False">
<Setter Property="IsEnabled" Value="False"/>
</Trigger>
</Style.Triggers>
</Style>
</fluent:SplitButton.Style>
But I don't know if that would have any side effects, and I'm not sure if I'm overlooking something really simple to achieve this behavior, hence the question.
Related:
#467 (This behavior was once integrated as default but got reverted)
#720
Environment
The text was updated successfully, but these errors were encountered: