Audacity 2.3.0 Macro comment/requests

[NTO]

I am very pleased to see the expansion pf Audacity macro capabilities, but
I would like to see an addition: access to the menu command 'Export multiple'

I am currently trying to work around this missing command by driving the UI from an external keyboard macro app, and have this problem:
When I get through the dialog that is the macro I wish to execute, the dialog does not close after I apply to project (e.g. Alt O,M,P). There is an OK button there, but it's not accessible by hot/keystroke.

IMO, dialog should close for process completion, but multiple executions was thinking(i suppose). Keystroke the OK to get out would likely work for me then...

[steve]

I would like to see an addition: access to the menu command 'Export multiple'

Perhaps the other way round:

"Export Multiple" could become a "special case" interface for a "macro".
The only reason that we can't currently implement "Export Multiple" as a macro script is that we don't currently have access to "Export Selection".

The benefit of implementing "Export Multiple" as a macro script is that it would then be relatively easy for users to create customised versions of "Export Multiple" (for example, exporting every other labelled selection, or export multiple based on audio clips.)

Another benefit would be that "macro scripts" may themselves be used as macro commands (with some limitations).

[NTO]

The only reason that we can't currently implement "Export Multiple" as a macro script is that we don't currently have access to "Export Selection".

Not sure what you are saying here.
Export multiple is an existing menu tree: File > Export > Export Multiple.
The parameters are there for its existing functionality.

[steve]

"Export Multiple" is currently a sequence of actions that is hard coded (in C++) in Audacity.
What I'm suggesting is that rather than extending the "Export Multiple" command so that it can be used as a macro command, it could be removed and replaced with a macro.

Macros may be called in macros:
If you create a macro called "Do Stuff" that runs a sequence of commands, then you could write another macro called "Do more stuff" and have "Do Stuff" as one of the steps. When "Do more stuff" runs and it gets down to the "Do Stuff" macro, the commands in "Do Stuff" will be executed as defined by "Do Stuff".

So if "Export Multiple" was a macro, rather than a hard coded C++ command, you would be able to use "Export Multiple" in a macro.
If "Export Multiple" was a macro, you would also be able to create custom versions of Export Multiple as macros.

So in short, what I'm suggesting is a way that your feature request could be implemented that is more versatile than just adding access to the existing menu command 'Export multiple'.

Does that make sense?