On Wed, Jan 11, 2012 at 4:35 PM, Juraj <[email protected]> wrote: > *EVERY* time I got a bit creative with applying clone nodes and other > advanced Leo features to my workflow (managing JSP files using @shadow nodes, > sometimes I edit the files in Eclipse as well), I really ran into "lost > data/leo crashes/unreadable files" kind of bugs.
Thanks for these comments. The integrity of Leo's data is paramount. Please report any kind of bug that causes lost data. It sounds like you may be suffering from clone conflicts. This will be the source of "uncached read node changed" conflicts. I know of no problems with these messages: they indicate something unusual or dubious has happened. If you don't like these messages, then perhaps you should dial back your usage of cross-file clones. You raise two completely separate issues, and it's important not to conflate them. The question of Leo's *stability* is completely independent of the bugs you mention. Indeed, I consider Leo to be stable if and only if new (daily) versions do not introduce *new* bugs. I stand by my assertion that Leo is stable in this sense. As for @shadow, I personally do not use it, but some people prefer it to @auto, and it's not going to go away. Again, if you experience data loss with @shadow I want to hear about it. 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.
