On Saturday, March 21, 2015 at 7:43:48 AM UTC-5, Edward K. Ream wrote: > 1. *Discover why the gnx's collided*.
I have not been able to recreate this problem. Boo hoo. Most gnx problems are intermittent. An unusual *sequence *of steps must happen for problems to manifest themselves. Bug #163 <https://github.com/leo-editor/leo-editor/issues/163> may be related. It (or something similar) exists Leo 5.0 final. Lacking other ideas, I am going to move on to... > 2. *Permanently activate all gnx checks* Leo may as well get the best checks now. > 3. *Get rid of the gnx caching scheme* This will clarify the situation. *fc.gnxDict:* This is the likely culprit if problems persist. Problems updating the gnxDict will create time bombs. I have initiated a thorough review of this dict using several sets of clone-find-all searches. The tempOutline keyword arg to c.pasteOutline stands out as highly dubious. Improved consistency checking is revealing problems that have existed since 5.0 or even earlier. We shall deal with this systematically before 5.1 b1. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
