Is SF itself scriptable? I'd love to make a macro that'll type "sf.ui.protools." and "sf.ui.protools.appActivate();" etc with a single keystroke. It'd save a lot of typing. (I'm aware of and use auto-complete but a one-key macro would be ace).
Christian Scheuer @chrscheuer2020-07-01 14:24:07.649ZYou should be able to use a Type Text action for this, I believe.
Chris Shaw @Chris_Shaw2020-07-01 21:11:57.645ZHmmm.
Doesn't seem to work.
Christian Scheuer @chrscheuer2020-07-02 13:17:04.526ZWorks just fine here. Give us some more info than "it doesn't work" and it's gonna be easier to help.
For example, show us what you were doing, how you assigned a trigger to it, and then when it didn't work, what exactly happened.- Chris Shaw @Chris_Shaw2020-07-02 17:26:12.171Z
Sorry for that Christian. It's been a hectic week of revisions
I created a Type Text action and assigned it to shift - F4 when SF is the focused app.
When triggered nothing happens - no errors either.
But when assigned to all apps it does work within SounFlow.
Perhaps org.sounflow.sfsx isn't the proper app that needs to be focused? It's the only one available in the application dropdown menu. I also get the same results when I browse for SoundFlow.
- Christian Scheuer @chrscheuer2020-07-02 17:42:19.002Z
Ah yea.. Gotcha. Due to how SoundFlow runs as both a background service and then, optionally, as the UI, it has different bundle IDs.
So, effectively, you cannot limit your trigger to only work in SF, it has to be global.- Chris Shaw @Chris_Shaw2020-07-17 20:16:07.308Z
One workaround I'm starting to use is to define
const sup = sf.ui.proTools
at the top of a script.Saves a lot of typing :)