On Thursday, January 5, 2012 11:58:48 PM UTC+7, mdb wrote: > > I will explain in a future posting about the problem of "an outline > losing its clones" > Aha, “to err is human, but *to really foul things up* you need an automated process”. 8-)
It actually comes from creating and using a DB system to store and > read nodes. I'm sure I wouldn't be able to understand it, but as you've seen recently, many people on the list would be interested in more detail on such a beast. Perhaps Terry's approach of UNLs+scripting would be a possible solution, he apparently doesn't use cloning at all. If the contents of your outlines are automatically generated, then there shouldn't be any problem with their UNL "addresses" getting out of sync - I believe that's the usual reason people don't use them more. And with sufficient programming foo, maybe a third alternative for your cloning issue would be to create a branch and demonstrate how you think that behavior could be improved, although I believe the fundamental data model is more or less "cast in stone", based on past developer statements here. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To view this discussion on the web visit https://groups.google.com/d/msg/leo-editor/-/HCVYRDsQRH8J. 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.
