On Sun, Mar 8, 2020 at 12:05 PM vitalije <[email protected]> wrote:
> If we are speaking of "fixing 1437" properly, I have to say that the more > I think about this bug, the more I am sure that the real problem is not > inside createFirstTreeNode. This method is doing a quite normal, natural > thing. > I agree. Perhaps I wasn't clear in the posting. It should not be an error to have two nodes with the same gnx in two > separate outlines. > It isn't an error. Paste retaining clones is intended to work between outlines. This command retains gnxs. The bug 1437 is about exactly this. > Hmm. Maybe not exactly this, but close. Commander created using leoBridge, has an outline with some freshly created > gnx, then it replaces the whole outline with the new one read from the > file. If that outline (read from the file) contains the node with the > exactly same gnx, it fails to read it correctly. > That's what Bob asserts, and I believe him. I think there is no sense in keeping the content of c.fileCommands.gnxDict > when loading completely new outline. > Yes, that might work. However, I believe the code I pushed also works. Let me know if it doesn't. 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS2MBQyHdZ3Ho8s1PJ7b4aj3RLdPpNCHH7HLmQ9rONo%3DPA%40mail.gmail.com.
