CheckCommand

Remarks: Subclasses may override the standard behaviour so that hierarchy of widgets can be taken into account. For example, a Control may return the data context of a parent, if it is not set explicitly.

Remarks: This allows you to use a command to define menu/toolbar items or other functionality, and use a delegated command to chain to when invoked. This is especially useful when binding to a view model, you can do something like the following:

var myCommand = new Command { MenuText = "My Command", Parent = myForm };
myCommand.BindDataContext(c => c.DelegatedCommand, (MyModel m) => m.MyModelCommand);

//...

myForm.DataContext = new MyModel { MyModelCommand = ... };

The ICommand.CanExecute(object) will also used to set the enabled/disabled state of the current command.

Remarks: This can be used to identify a command.

Remarks: On some platforms, the menu bar does not show the image by default (e.g. OS X). You can override this behaviour using a style on the handler.

Remarks: This can be used to determine when to allow certain logic during the update of the data context. It is used to disable binding setters on the model when the data context changes so that a binding does not cause the view model to be updated when the state hasn't been fully set yet.

Remarks: Implementors may override this to fire this event on child widgets in a heirarchy. This allows a control to be bound to its own Command.DataContext, which would be set on one of the parent control(s).

Remarks: This may be fired in the event of a parent in the hierarchy setting the data context. For example, the Container widget fires this event when it's event is fired.