Ancestor @<file> nodes must be marked dirty if the value of what is supposedly the same clone conflicts.
This happens in the uncached read code, and gives rise the the "changed" messages. The new code will likely be easy to implement. Just compare the old and new version of cloned headline and body text in v.createOutlineFromCacheList. It should be clear why marking changed nodes dirty is necessary. If we didn't do that, updating a clone would change all the clones in the outline, but if we didn't mark the changed nodes dirty we would not update thin files properly. For example, suppose a clone in @thin x.py overrides a clone in @thin leoProjects.txt. We must mark leoProjects.txt dirty if we want to put all clones back in synch. This is not a theoretical situation: I saw it happen earlier today. 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 -~----------~----~----~----~------~----~------~--~---
