WPF: MVVM - disable button if command is null

Question

I have binding on some command:

<Button Command="{Binding Save}" />

Save is command of some object that can be selected from list. In initial state there is no any selected object so binding does not work and CanExecute does not invoked. How can i disable this button using MVVM?

Solution: WPF/MVVM: Disable a Button's state when the ViewModel behind the UserControl is not yet Initialized?

Guys, thanks for your answers and sorry for duplication of question.

You could create a Style for the Button with a DataTrigger that disables the Button when {Binding Save} equals x:Null. — Heinzi, Mar 03 '11 at 12:37
Thanks! I found the same solution: http://stackoverflow.com/questions/4423746/wpf-mvvm-disable-a-buttons-state-when-the-viewmodel-behind-the-usercontrol-is-n/4424241#4424241. But i can't mark your answer as accepted. — Rover, Mar 03 '11 at 12:45
Thanks. I've added my comment as a "real answer" (and took the liberty of adding your link), so you can accept it now. :-) — Heinzi, Mar 03 '11 at 16:55

HCL · Answer 1 · 2011-03-03T12:46:13.510

8

Define a command that always return false to CanExecute. Declare it at a global position such as in your App.Xaml. you can specify this empty-command then as the FallbackValue for all your command bindings you expect a null value first.

<Button Command="{Binding Save,FallbackValue={StaticResource KeyOfYourEmptyCommand}}" />

edited Mar 03 '11 at 12:46

answered Mar 03 '11 at 12:36

HCL

36,053
27
163
213

score 6 · Accepted Answer · edited May 23 '17 at 12:18

6

You could create a trigger in XAML that disables the Button when the command equals x:Null.

An example can be found in the answer to this question: WPF/MVVM: Disable a Button`s state when the ViewModel behind the UserControl is not yet Initialized?

edited May 23 '17 at 12:18

Community

1
1

answered Mar 03 '11 at 16:55

Heinzi

167,459
57
363
519

score 1 · Answer 3 · answered Mar 03 '11 at 12:30

I'm not sure you'll be able to achieve this. However, an alternative would be to initialise the Command object initially with a basic ICommand where CanExecute simply returns False. You could then replace this when you're ready to put the real command in place.

score 1 · Answer 4 · answered Mar 03 '11 at 12:34

1

Have a look at the Null Object Pattern

answered Mar 03 '11 at 12:34

Dennis Traub

50,557
7
93
108

score 1 · Answer 5 · answered Mar 03 '11 at 12:41

Create a NullToBooleanConverter and bind the IsEnabled property to the command, running it through the converter:

class NullToBooleanConverter : IValueConverter
{
    public object Convert(object value, Type targetType, object parameter, CultureInfo culture)
    {
        return value != null;      
    }

    public object ConvertBack(object value, Type targetType, object parameter, CultureInfo culture)
    {
        throw new NotImplementedException();
    }
}

Then

<UserControl.Resources>
   <Extentions:NullToBooleanConverter x:Key="NullToBooleanConverter" />
</UserControl.Resources>
<Button Content="Hello" IsEnabled="{Binding Save, Converter={StaticResource NullToBooleanConverter}}" />

WPF: MVVM - disable button if command is null

5 Answers5