On Tue, Mar 17, 2009 at 9:21 AM, Edward K. Ream <[email protected]> wrote:
> > This is a mystery that must be resolved. > The fix is on the trunk at 1656. The problem was a cloned << imports >> node shared by the nodeActions and fileActions plugins. The two cloned nodes were actually not the same in the two external files. The fix was to unclone the nodes, and to add an "import re" to the section in the nodeActions file. This may be a subtle write-logic bug. My guess is that setAllAncestorAtFileNodesDirty did not mark both nodeActions and fileActions dirty when the shared << imports >> node was changed. But this is a guess: conceivably a change was made when only one @thin node was present. Or something. Pretty hard to say for sure. In any case, Leo did right to complain. Please, give us all a break and DO NOT use cross-file clones in @thin nodes. Thanks. 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 -~----------~----~----~----~------~----~------~--~---
