Macros are one of the cornerstones when working with eos and with increasing demands for automation on Shows the current workflow starts to lag behind when it comes to editing, copy/pasting, Incrementing values across a range of macros.
Implementing these features inside the Marco editor for eos is easier said than done and would be a major change like people on this forum said before.
Here's my proposed Feature (which is hopefully less invasive than rewriting the whole macro editor)
Make Macro contents available for editing in the .csv format. This way you could export your macros and edit them outside of eos with exel for example which has powerful tools for editing values. There could be a "Macro Syntax Dictionary" like there is a "OSC Dictionary" in the Manual to ensure that the text is formatted correctly for import into eos.
This is fwict integrated nicely for Show control for example:
I could easily build 1000 Links to 1000 Subs in 10 minutes within a .csv like this
This is not the case for macros since macro contents are not exported at all or being encoded as gibberish.
I'd love to hear feedback to this proposed solution. Is this a good idea?
Thanks
