On Apr 8, 9:51 am, "Edward K. Ream" <[EMAIL PROTECTED]> wrote:
> The question is, what does this mean :-) I think the short answer is that
> the present scheme, involving descendentTnodeUnknownAttributes, does not
> allow information contained in vnodes in @thin trees to be saved. However,
> a plugin could create a foreign attribute of the **root** vnode of the @thin
> tree. Leo would save this attribute as usual (in the .leo file), and with
> enough cleverness the plugin could associate info in this attribute with
> (reconstituted) vnodes. It won't be pretty, but it might be possible.
>
> HTH.
>
> Edward
I haven't played with vnode attributes, but as a workaround, might one
have a clone of an @thin's child node outside the @thin descendants,
and keep the attributes in the .leo file?
- Stephen
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
