The triggering mechanism issue of CanCommand

[869570967]

I found that CanCommand's detection mechanism only checks whether the properties in the current VM have changed, and does not check the properties of the Model object in the VM, for example.

This writing style can trigger CanCommand when the property changes. But the method below doesn't work, is there any way to make the method below support it?

[869570967]

Because I am accustomed to placing all properties within the Model object, the VM object only needs to exist with one Model object. The VM mainly consists of commands and business methods, which is equivalent to extracting properties into the Model to prevent the VM from becoming too bloated.

[vb2ae]

Typically I do not declare the updatesource in the binding but the features sample does have an example on the actions page which enables some of the buttons when text is entered into a textbox