johnf wrote: > Larry (who is not a member of dev) has presented code to eliminate recursive > calls in dPermixin.update() on the user list. All the code does is to insure > that only one self.Form.update() is active at one time. IOW before a new > update() can be started the current one has to finish. > > Does anyone consider this a good proposal? Is it required?
I think it sounds good, but haven't had a chance to check it out yet. Not sure it's required, but if it doesn't hurt, and if it improves performance then I think it is a slam-dunk. > I for one can recall when I first started that I called update() all over the > place in my code. I was under the mistaken impression that it was required. > It is still required with code that makes changes to the underlying datasets. > I hardly ever call update(). If I do, it is only on the outermost container that needs it, which is usually a single control or a handful of controls. Why force all that work on the form when it isn't needed? Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]
