Component search - how does it work?

[Orvillain]

Component search seems a bit iffy to me. If I search for something like "Engine1SamplerTabArea" then depending on what the names of my other components are ... I might end up with a load of stuff in the results that just isn't anything remotely to do with my original search term.

How does it work?

[Chazrox]

@Orvillain What method are you using?

[Orvillain]

@Chazrox In the UI editor, the foldable panel on the left hand side that shows all of your added components. There's a search box at the top of it, but it is a bit ropey.

[Chazrox]

@Orvillain oh, I thought you were using a function to search. Dont mind me. lol,.

[dannytaurus]

@Orvillain TIL there's a search box at the top of the Module Tree panel! How did I never notice that!

Very handy for busy module trees!

According to the HSIE source code, it matches based on several things, including module name, module type, module parent, and module children. This might be why it's showing results that don't seem related.

So if you search 'reverb' it will show all modules that have a reverb in their child hierarchy, which shows a lot of unrelated info.

It also uses a fuzzy search that might be matching close, but not exact, results.

[dannytaurus]

@Orvillain Also, to clarify, it only searches the Module Tree structure. It doesn't search the Interface Designer for UI components, nor any script content.