When using the MVVM pattern I get around this by creating a "flat" viewmodel, ie does not have nested child objects. Using something like automapper, its a breeze moving from the nested object model to the flat model and back
Heinrich On Mon, May 2, 2011 at 5:19 PM, Greg Keogh <[email protected]> wrote: > Folks, in dialog-like screens with OK/Cancel buttons and a bound data > object I like to implement and listen to INotifyPropertyChanged on the data > object so I know the screen is “dirty” and I enable the OK button. > > > > When the data bound object is composed from a nest of other objects, it > becomes impractical to pass changed events up through the levels of objects > to the top. It can be done by manually sending the event up through > child-parent objects, but the code to create this sort of “event bubbling” > is verbose and tedious. > > > > Is there some trick that I’m not aware of for creating mock property > changed “event bubbling” in my own nested objects? > > > > Greg > > > -- Heinrich Breedt “Do not wait to strike till the iron is hot; but make it hot by striking.” - William B. Sprague
