Timeline for How should multiple ViewModels communicate in a larger WPF MVVM application?
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 14 at 15:09 | comment | added | Craig | @Sam I've done it both ways, one implementation like this that did pass a reference down, one that did not. The time I had a back-reference, it was because I needed something from two levels down to communicate up to the main view model. Maybe there would have been another way of doing it without the back-reference. In each case, it was mainly a one-off and not something where I was worried about re-use in a different context. | |
| Aug 14 at 15:06 | comment | added | Sam | thank you very much. Having my "child" ViewModel have a back-reference to the main view model, would make it almost impossible to re-use. | |
| Aug 14 at 14:56 | history | answered | Craig | CC BY-SA 4.0 |