On Sun, Nov 6, 2011 at 2:20 PM, Kent Tenney <[email protected]> wrote:
> Right. When I discovered this, I felt like it should be examined, but without > clarity on where I was going. Ok. > Is it a symptom of code which is overly complex, a candidate for improving > the code base by simplification? More likely, it's just a symptom of unused code. Perhaps it worked in the Tk world and was lazily ported to Qt. No telling, really, and it's not too important. > My expectation was for one call per each unselecting of a node. If it's > possible to provide that behavior, it would simplify writing code hooked to > the event: as it is, I expect I'll come to the point of needing to keep track > of which of the several calls I'm currently in. I'll see what I can do. It *might* be possible to prevent multiple calls, but event lockouts can be tricky to get right. Stay tuned. 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.
