[FEATURE REQUEST] Less macro indirection

[danielo515]

Hello, and thank you for this great plugin. This more than a feature request is a question about why macros require so much indirection. It seems not possible to select several macros in the select macro option, so I don't understand why a separate step is needed. Why have a button to manage macros, and another button to create a new macro choice if all you can do in the macro choice is say which macro to execute? Why not just allow to configure the macro directly from the macro choice? The only use case I can think of, is if you want to alias your macros, but that's all

[plufz]

I have the same question. It seems like an unnecessary step that causes confusion. I would really like it if the macro manager and current macro choice dialog was removed and creating a macro choice just showed me the macro dialog without the extra step we have today.

[chhoumann]

Hey! I agree that the UX isn't perfect. The idea was to separate macros to be their own thing, which let me support reuse of macros across choices and other macros., as well as additional choice-specific configuration.

At this point, I think the direction I was going with this feature won't be using the indirection as I had intended, so I'm for changing QuickAdd to simply have macros, and not the additional layer of indirection. This would also mean the removal of the macro manager.

Here's what I'm thinking:

• Remove macro manager
• Ensure 1:1 relationship between macro choice and macro - remove the indirection so the macro builder starts instead of the menu with the dropdown we have now. I'm a bit on the fence if we should migrate macros into choices or keep them separate and just handle the extra logic of renaming in two places. Essentially keep them synced or unify somehow.
• Allow QuickAdd 'choices' to be run on startup (current macros feature). Macros only to start(?)

[github-actions[bot]]

:tada: This issue has been resolved in version 2.0.0 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket: