Allow searching under Macro Run (Action) and Enable/Disable Macro (Action + Constraint)

[chaoscreater]

When configuring an Action using Macro Run, or when configuring the Enable/Disable Macro as an Action or Constraint, it's quite hard to quickly find the macro that you want. This is especially annoying when you get to 100+ macros. Sure, you can "Enter Macro Name", but you'd still have to type out the whole thing and you may not necessarily remember it. Searching for keywords or a substring is much quicker and simpler.

With the introduction of the Action Block feature, you can easily search for something and find it super quickly. It would be nice if we can have the same consistent search interface for Macro Run and Enable/Disable Macro as well. Of course, if any other Actions or Constraints can benefit from a proper search interface, then include them too, e.g. searching Variables for use as a Constraint or whatever.

 

[Endercraft]

When configuring an Action using Macro Run, or when configuring the Enable/Disable Macro as an Action or Constraint, it's quite hard to quickly find the macro that you want. This is especially annoying when you get to 100+ macros. Sure, you can "Enter Macro Name", but you'd still have to type out the whole thing and you may not necessarily remember it. Searching for keywords or a substring is much quicker and simpler.

With the introduction of the Action Block feature, you can easily search for something and find it super quickly. It would be nice if we can have the same consistent search interface for Macro Run and Enable/Disable Macro as well. Of course, if any other Actions or Constraints can benefit from a proper search interface, then include them too.

I can confirm that if you forgot the name of the macro that you would like to use for action / constraint but you know that you can recognize it by reading it and start looking through the 331 others macros... It takes time.

 

[chaoscreater]

I can confirm that if you forgot the name of the macro that you would like to use for action / constraint but you know that you can recognize it by reading it and start looking through the 331 others macros... It takes time.

That's what I'm currently doing now and it's inefficient.

Macros shouldn't be named just to make it easier for you to find them at the top of the list. Macros are named based on other conditions and preferences.

If you have 500+ macros, you're wasting a lot of time renaming the macros, searching for them iteratively, etc. It's just not a good approach.

We already have a proper working search interface under Action Block. It's just a matter of making that same search interface available for other areas.