On Jan 29, 7:55 am, "Edward K. Ream" <[email protected]> wrote:
> I can't wait until the bug can be replicated easily. That's
> not guaranteed ever to happen. Instead, I'll examine the entire
> selection logic again and try to deduce any possible race conditions
> from first principles.
I've just added a good simplification to event handlers, and any other
method that uses lockouts. nativeTree.busy returns True if any of the
lockout vars have been set. So all methods that set lockout start
with::
if self.busy(): return
Actually, self.busy() returns a string telling which lockouts are set,
so methods can report unexpected busy conditions as follows::
if self.busy():
return self.error('busy! %s' % self.busy())
Already, putting this pattern in place has revealed some problems.
I'll be upping the new code after I test it awhile.
Edward
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en
-~----------~----~----~----~------~----~------~--~---
