It’s great to hear that Actions are helping to open up Studio to everyone
The ability to control an audio file is a good suggestion, I’ll pass this on to the team.
Calling a script from an Action however seems like it would conflict with the intended purpose of Actions i.e. allowing users to perform functionality without the need to write any code. Your suggestion would mean a user would have to write some code in a script, before being able to call it from an Action.
To better illustrate this, we can use the examples below. Currently, Actions are compiled to script when the experience is previewed/published meaning this:
…does the same as this:
Using the suggested method would result in something like this:
…where the On Tap Action would call the function from a script node:
As you can probably tell, it makes things a bit more complicated than it needs to be as it separates the functionality and would require simultaneously managing the Actions on your node, and the code within your attached script to avoid conflicts.
You would also have to write the function manually, at which point it might make more sense to also manually wrap it in a relevant event handler.
For these reasons, this isn’t something we’re currently looking to implement, but rest assured we are definitely working on expanding our Actions functionality!
Thanks again for your suggestions @donnav & @higor, we really appreciate your enthusiasm for ZapWorks!
Any other questions feel free to let me know, and keep us posted on how your projects are coming along.
All the best,