On 10/2/10 7:04 AM, Jacek Kałucki wrote: > Użytkownik Ed Leafe napisał: >> On Oct 1, 2010, at 7:55 PM, Paul McNett wrote: >> >> >>> I have some commonly-used dialogs tied to bizobjs that I hide() instead of >>> release() >>> for optimization purposes but when I navigate the main bizobj, update() is >>> occurring >>> for the hidden dialog, and sometimes there's no record in the bizobj at the >>> time, >>> causing an exception. Also, it seems like a waste of cycles to update >>> something that >>> isn't Visible anyway. >>> >> >> The one thing that I think might be problematic is that when you set >> Visible=True, the form/dialog might be showing stale values, so you'd have >> to add a call to update() at that point.
> Overwrite update() method and use additional semaphore like '_pendungUpdate' > when Visible property changes to true, then call update after. What about just unconditionally calling update() when Visible changes to True? This will still be better than the status quo, which has update() being called on non-visible objects, and is simpler to explain and understand. 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]
