On Thursday, December 5, 2013 7:41:19 AM UTC-8, Edward K. Ream wrote: > > > The intention for "clone wars" is that the last clone loaded by Leo > "wins". >
Thank you. Your reply helped me quite a bit. But what does "last clone wins" mean? My first guess was that the header and body of the node are taken from the last occurrence in tree order of the cloned node and the prior occurrences are ignored. But two simple test cases proved this wrong. Test case 1: The cloned node in the .leo file is before the cloned node in the @file. Leo-Editor used the @file contents and generated "Recovered Nodes. Test case 2: The cloned node in the .leo file is after the cloned node in the @file. Leo-Editor behaved the same. Leo-Editor used the @file contents and generated "Recovered Nodes. That is, the "last clone" lost. I have been unable to determine what makes Leo-Editor silently ignore changes in the @file. I have seen this several times. Once it happens it is repeatable. But because I have been unable to determine why, I have been unable to make a simple test case. Perhaps Leo-Editor ignores some or all data in the @file when the @file data is in the Leo-Editor cache? I don't know how to confirm this. What makes Leo-Editor silently ignore changes in the @file? -- 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/groups/opt_out.
