Fuzzy Finder: Search within selected category only

Hendré Page 4 years ago updated by Lazlo Bonin (Lead Developer) 2 years ago 8 2 duplicates

It would be great if it was possible to search only in the selected category. 

Bolt Version:
Unity Version:
Scripting Backend:
.NET Version (API Compatibility Level):

Duplicates 2

Under Review

Hi Hendré! Welcome to the community :)

That's an interesting suggestion. What would you see in terms of user experience (UX) for this? A checkbox on the fuzzy window? A special character in the search field?


This is a great idea,  a check box maybe at top right of fuzzy would be more obvious for everyone. Like while checked, it'll always search the same folder and it's children. Sounds pretty useful.


Hi, my suggestion is whenever user click or enter a category from fuzzy finder result then type something, it is automatically search keyword in that category. 

If user want to search in all categories, then user must press backspace all the way to the root, or maybe press *ESCAPE* (edit) to reset the fuzzy finder. 

I hope you can understand what I mean. 😀


Ahhh yes, that makes a lot of sense!

Switching this to planned, I'll try to cram it in the v.1.2 cycle.

@Lazlo, sorry did not see your message. I think Gulpi's suggestion makes the most sense!

Good news!  Lazlo has heard our pleas and has plans for this!  An overhault to the search is currently slated for 1.4 (Workflow improvements).


However, the specific feature you are asking for, he has stated as wanting to squeeze into 1.2.X,  as mentioned in the comments here:


So maybe he's open to bribes.


I'm thinking about the UX of category search further. Current idea:

  • When searching, you search anything below the current point in the graph
  • When entering a child node, if you had a search bar, it clears to allow for further filtering
  • When going back up, your previous higher-level search is preserved

Basically, searches will be saved "per level".

If I can fit in a "breadcrumb"-like display in the search field I would, but it might be too tight.

I'm hoping the search won't be slowed down too much by filtering, because the search code is currently global, so there'll need to be an additional check to verify that the items are children of the start node.


Cleaning up old issues! This was completed in v.2.0.0a3.