El 31/03/12 10:24, Ed Leafe escribió: > On Mar 30, 2012, at 10:28 PM, Paul McNett wrote: > >> I don't think an observer would even be needed. The dynamic properties are >> already >> properties, with getter methods. So, the evaluation of the dynamic property >> simply >> needs to happen in the dynamic property's getter. > I looked over the code, and I have a few ideas that might make this > simpler. > > First, the methods for the dynamic updates are dunder methods, making > them inaccessible from outside the object being updated. We need to either > change them to "public" methods, or provide a public method that will in turn > call the dunder methods. > > Second, I think we need to raise two form-level events: > > 1) ValueChanged, which would be raised when any of the form's controls raises > a ValueChanged event. This would enable objects to respond when any control > on the form changes its value.
Some way to find out which control raised the ValueChanged event? > 2) FocusChanged, which would be raised when focus changes from one control to > another. This would enable controls to respond to the user navigating within > a form. Same thing, some way to access to a (fromControl, toControl) tuple which indicates both controls involved in the FocusChanged event. On a side note, a problem that always bit me in VFP was that when I had a textbox's validation and a cancel button for the form I had no way to indicate that if the user hit cancel button the validation should not be performed. Is there a way in Dabo to check where the focus is going in the validation event? _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[email protected]
