2

I've been using the RelayCommand a bit here and there, and it got me to wonder and want to know... when exactly does the CommandManager.InvalidateRequerySuggested() get called by WPF?

My guess is every time any other routed event on UI get's triggered, which in the MVVM world primarily means when the the OnPropertyChanged event is raised, causing the value to change, causing some related routedevent to execute. But, that's just a guess, I'm wondering if anyone knows the exact inner workings here.

myermian
  • 31,823
  • 24
  • 123
  • 215

1 Answers1

2

There are a few causes I know of:

  • When keyboard focus changes.

  • After a command is executed.

  • Controls can invoke this when as they deem necessary in some other cases (for example when you press a key while in TextBox).

Property change alone is not generally a reason for invalidation (I guess for performance reasons).

Sadly, I failed to find any documentation about this in MSDN. What I posted here is based on what I found in Pro WPF in C# 2010 (great book BTW).

Also, its not the CommandManager that gets invalidated. The CommandManager merely sends an event (to which controls using commands subscribe), so they can update their enabled/disabled status.

Matěj Zábský
  • 16,909
  • 15
  • 69
  • 114
  • This pretty much covers the scenarios I've noticed that end up causing the CommandManager to requery `CanExecute`s. I've still ran into some scenarios where I need to manually kick the CommandManager into gear by calling `CommandManager.InvalidateRequerySuggested()`, though - usually after a `PropertyChanged` notification, which, as mentioned, does not cause invalidation on its own. – Aphex Oct 05 '11 at 17:25