Gentlemen, At the risk of raising the "W" word, I ran into this issue when activating a DynamicVisible with a statement issuing a callAfter inside the called method. Then, when testing in...here I go...Wing, the error surfaced when I closed the form. Could not a similar occurrence happen elsewhere?
Larry -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul McNett Sent: Saturday, November 22, 2008 6:33 PM To: Dabo developers' list Subject: Re: [dabo-dev] Suggested mods to callAfter (et al)to test for dead objects Ed Leafe wrote: > On Nov 22, 2008, at 9:50 AM, Paul McNett wrote: > >> This idea sounds reasonable to me. Ed? > > > I haven't seen this happening, so I'm not sure what sort of problem > it is we're trying to fix here. > > The after* methods should all be called before the release of their > object. I can see the possibility of cases where you issue self.callAfter(), and the function gets registered fine, but then when it comes time to execute the function the object is dead. Paul [excessive quoting removed by server] _______________________________________________ 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]
