You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Seems currently only the note text can be searched for results in other
note tabs by checking "Search All notes". If the text I'm looking for is in
the tree structure of another note, I get "pattern not found", even with
"Search all tree Nodes" checked. Using version 1.7.8
Original issue reported on code.google.com by Esteban...@gmail.com on 25 Feb 2010 at 3:33
The text was updated successfully, but these errors were encountered:
To find repeated identical node names an F3 continue search would be handy. For the moment you have to type CTRL+F again and again.
Indeed, exists a command: 'Find Next Node'. But, since version 1.6.5 it has default shortcut Shift+F3 assigned (and undocumented, I think), and that shortcut conflicts with 'Cycle Case' (takes precedence).
Probably, it would be better to also use F3 to find next node (if last search operation was Find Node). Besides, in most cases focus will be in the tree panel.
Now, Ctrl+F and F3 (or actual hotkeys) will call to 'Find...'/'Find Node...' or 'Find Next'/'Find Next Node' depending on the tree panel having or not the focus.
Also, the command 'Find Next Node' will search all the notes and/or all the hidden nodes depending of the options selected in the find tab of the Resource panel ("Search all notes" and "Search hidden nodes")
Closes issues #286 and relates to a minor enhancement indicated in #461 and #156
Signed-off-by: Daniel Prado Velasco <dpradov@users.noreply.github.com>
Now, Ctrl+F and F3 (or actual hotkeys) will call to Find.../Find Node... or Find Next/Find Next Node depending on the tree panel having or not the focus.
Also, the command Find Next Node will search all the notes and/or all the hidden nodes depending of the options selected in the find tab of the Resource panel ("Search all notes" and "Search hidden nodes")
Original issue reported on code.google.com by
Esteban...@gmail.com
on 25 Feb 2010 at 3:33The text was updated successfully, but these errors were encountered: