On Wednesday 19 December 2007 10:44:05 am Bill Anderson wrote: > > 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
I know you asked Ed this question but it makes sense that if a control required information on the state of another control (i.e. Enabled) that it be kept at the UI level. Also custom controls, or composite controls (made from dabo controls) may require direct interaction. -- John Fabiani _______________________________________________ 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/dabo-users/[EMAIL PROTECTED]
