I have a dForm with, among other things, a couple buttons with captions
"Sign In" and "Sign Out". The onHit() handlers call
self.getBizobj().signIn() and self.getBizobj().signOut(), because
there's logic there that really belongs at the business logic level
rather than the ui level.
Part of the logic of the biz.signIn() method will add a new record to
the bizobj and save the changes immediately.
With me so far?
The problem is, it is more convenient to call dForm.new() instead of
biz.new(), because of the nice side-effect of dForm's new() raising the
RowNumChanged event - the data-bound UI controls will refresh themselves
automatically. My only options are:
1) Call back to the Form's new() from within the bizobj, instead of
calling bizobj.new() directly. Yuck.
2) Raise the event manually, myself, and remember to do this.
3) Put this biz-level logic in the form's method, and call the form's new().
Would you be opposed to having dBizobj raise the OnRowNumChanged event
whenever there is a change in RowNumber? dForm could be configured to
bind to that event and then re-raise it for the ui controls to bind to.
--
Paul McNett
http://paulmcnett.com
http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
