> > > > The form is a lot "smarter" than any of its controls, and > "knows"about its bizobjs and how to talk to them. > > So in your case, the button should only tell the form that it has > been clicked. After that, the button's job is done. It does this by > calling the appropriate form method; it is in this method that you > handle the communication with the bizobj. > > While typing this, I see that John has responded to your question, > and with all due respect, his answer is wrong. Buttons should never > "know" about bizobjs, much less try to directly manipulate them. They > should talk with the form, and occasionally to sibling controls, but > never beyond that.
Ed -- OO question -- when should a control know about a sibling control? I'm trying to think of a case where that would be true and I can't come up with one... Bill --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: Dabo-users@leafe.com 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/dabo-users/[EMAIL PROTECTED]
