I'd argue for not disabling Ok, regardless of whether the page is dirty or not. Just run with evaluating dirtiness after ok is clicked. It makes documenting easier, and running someone thru doing something over the phone easier.
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 > > > -- Meski "Going to Starbucks for coffee is like going to prison for sex. Sure, you'll get it, but it's going to be rough" - Adam Hills
