Ed Leafe wrote: > On Jul 8, 2008, at 12:08 PM, Paul McNett wrote: > >> An alternate (better?) way would be to override the image's update() >> method, as update() gets called when the form knows that the row >> number >> has changed (and other places, too): > > Right track, but IMO is better handled by a form-level modification. > Controls shouldn't know anything about bizobjs, so it would be cleaner > to have the form's update do something like this: > > def update(self): > self.super() > self.img.Picture = self.PrimaryBizobj.Record.imagePathField
It really just depends on the paradigm you want to use. Form-based makes a lot of sense, I'm not disparaging it. However, I tend to build at the panel- or control- level and have very little code at the form level. I like being more encapsulated and modular. The control doesn't "know about the bizobj" in my example, it merely knows that the form will know what to do. Paul Paul _______________________________________________ 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]
