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
Hi! It is sometimes confusing if I have one node selected and toggle search, then cycle through search results.
I think "selected node path" should be dropped at least, and it will be great if "selected node path" will follow the current selected search result, it would be super handy.
Case:
user searches for word "social" in a big json. Cycling through search results with auto-selecting current search result would be super handy since user could easily (without extra X clicks) see which json section (node path) is a parent of current search result.
Thanks in advance!
The text was updated successfully, but these errors were encountered:
Right now the navigation path shows where the current selection is. Probably the best solution is to clear the selection when cycling through the search results, and show the path of the active search result instead.
I've now implemented and published a fix that clears the navigation path whilst iterating through search results. Keeping the selection in sync with the active search results works out a bit odd (mixing two different things). Another future improvement could be to implement Ctrl+Click to switch focus from the SearchBox to the active search result for real.
Hi! It is sometimes confusing if I have one node selected and toggle search, then cycle through search results.
I think "selected node path" should be dropped at least, and it will be great if "selected node path" will follow the current selected search result, it would be super handy.
Case:
user searches for word "social" in a big json. Cycling through search results with auto-selecting current search result would be super handy since user could easily (without extra X clicks) see which json section (node path) is a parent of current search result.
Thanks in advance!
The text was updated successfully, but these errors were encountered: