On Aug 18, 2009, at 4:20 PM, Paul McNett wrote:
> Ed, what's your opinion of adding dForm.moveToPK(), and having that
> function call activeControlValid()?
-1
> Not that I'm against users calling activeControlValid() explicitly,
> but
> moveToPK() seems to me to be one of the places where it would likely
> be
> the desired behavior, and it would be consistent with the other
> navigation functions in dForm.
I think that we shouldn't code to exceptions. The only reason that
the call to activeControlValid() was needed is because of the order of
event firing didn't match what we needed. Most of the time, though, it
works just fine.
I also don't think that controls on a form should know about PKs,
datasets, and the like. They should at most call a form method to
handle their being clicked or typed in or whatever. They shouldn't
have to know that their node contains a PK and that when they are
clicked they need to talk to a bizobj, etc. They should simply call a
form method in their handler, and let the form take it from there.
-- Ed Leafe
_______________________________________________
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]
