Save Macros as Templates without converting to script?
or alternatively converting script back into original macros?
I'm not familiar at all with scripting so it's been a massive learning curve that I'm still at the very bottom of. I know it's been a frustration with others who I've tried turning on to SoundFlow as well.
If I build a set of actions, modify them, etc etc etc, it would be nice to be able to save that as a template that I can then tell (in the template tab) what to show/not show/etc. I THINK that's where SoundFlow feels like it's heading, and maybe something like that already exists. I just know when I create a template, it feels like a final step for me at my coding skill level. If I need to adjust something or change it, it almost feels easier to start over.
Brenden @nednednerbWithout an extra feature being baked in, could you accomplish what you are seeking with the following approach?
- When you get to a point with a macro that you want to template, put that somewhere in a user "package/folder" location in SoundFlow.
- Rename it to "....TEMPLATE"
- When you want to configure it for a purpose or "preset", copy it first.
- Make a template using the copy, place it wherever convenient, or leave all the presets in the same folder.
In the past, some users have mentioned the idea of a keyword, placeholder, or variable in macro-only template workflows.
Going from script back to macro, though, would be quite tricky to implement.Any extra code might just break the reverse translation. You might still have to be strangely specific and use specific conventions.
In that regard, figuring out the templates with the script could be your best bet if you have to otherwise convert to script anyway.Take your time; learning will get you there! Maybe you have a specific macro to look at. Click "Get help" in SoundFlow.
- BBrian Armstrong @Brian_Armstrong
That is a great idea, and somewhat similar to what I'm doing now. I have a "test" macro that is just kind of a graveyard for ideas, then each template I have can be traced back to a macro that I saved. It's part that, but also part stuff that isn't fully supported yet in actions (i.e. if you hold command key while pressing this stream deck button, it will do something different from when you hold the option key, etc) Or when I add something that then needs a property created for it, I have to know what to change and what to add to the "const" and where to add it, etc etc.
Maybe a partial solution would be just having more options when converting to a script. Like, a toggle for "make a property for this action when converting to script" or the ability to leave a note/comment for each action to help make the script easier to navigate.
Again, I fully acknowledge that for most of the users of this forum, this is all probably super easy for them, and I am getting the hang of things. Soon enough I'll have the time to figure it all out. Problem is, it'll be hard to find the drive to get it done when I don't have a deadline to meet. haha.
Thank you for suggestion. I have some tweaking to do for my process and this will help!