This behavior seems normal for me. I don't know the code, but seems, that every outline has it's own find tab and objects within. The default text in the Find field is "<find pattern here>", so when you hit the "Find next" evidently the result is:
not found '<find pattern here>' May be it could be fixed, by caching the search text in the Leo application object and the default search text of the outline could get this cache value if there is one. Only an idea, unfortunately I don't know the details. On Monday, September 15, 2014 9:27:24 PM UTC+3, Fidel N wrote: > > This was very difficult for me to understand, but I think this is it at > last. > > In order to reproduce this issue, please do the following: > > In the "Find" tab, check the "suboutline only" > > Select an outline, and search for any text on its subtree, for instance > "a". This outline shouldnt have "a" within its text. > > Now select another outline (that should have "a" within its text), then > click "Find next" or just do "F3" > > It should make the search again, this time within the subtree of the > selected node, but instead, it will give you "not found 'a'" > > It will only work if you change the search. So if you want to search for > the same term within another outline, you have to change that twice. > > I think this bug also interferes with searches not limited to the > sub-outline, but still wouldn't be able to pinpoint it. > > Did anyone else have problems with this or is it just me?? > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
