> > After reading the file, bridge.openLeoFile sets c.hiddenRootNode.gnx to a > value that doesn't conflict with any gnx in the just-read file: >
I am not convinced that the c.hiddenRootNode causes the gnx clash in the bridge. I suppose the first child of c.hiddenRootNode is the one vnode that can introduce gnx clashes in the bridge when opening two or more outlines within the same second. Perhaps in the bridge there is no need to create this first child at all. As I understand creating this first vnode is only necessary to allow user to see something in the outline even if it is empty. But in the bridge user doesn't see anything and perhaps the user of the bridge should be responsible to create this first node at the appropriate moment. When using bridge to open existing Leo file, there would be no need to create this node before opening the file. Vitalije -- 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/99c9e035-32ac-4498-b416-0e5d3a825328%40googlegroups.com.
