On Jan 22, 8:11 am, "Edward K. Ream" <[email protected]> wrote:
> There are still troubling aspects of the data problem. The problem > appeared to trigger code related to old @file nodes. This is the only > way, if I understand the situation correctly, that resurrected nodes > could damage the data in the way that I thought I observed. I may have found the source of the problem. The code in atFile.read() that determines whether an @file node is an old or new format by looking for a tnodeList attribute of the root node. But this attribute comes from the .leo file, not the external file! This is a dubious, fragile scheme. It would seem safer to look at the @+leo line of the external file. 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.
