Dynamic calls to procedures

Thanks for clarification. I agree that feature might be useful. We’ll consider it!

This is an interesting feature request, but I was wondering if I could make this work today in 2.14? We could write a simple dispatching function in the ExternalInterface. It would take two arguments, the name of the function to be called and the arguments to pass on to that function. It would look something like this:

	app.ExternalInterface.procedureCaller = function(procName, argsString) {
		app.ExternalInterface[procName](JSON.parse(argsString));
    }

For example, you could call it like this:
app.ExternalInterface.procedureCaller("myProcedure1","{'color':'red', 'shape':'sphere'}");

…but this does not work for ordinary procedure puzzles because their code is inside a closure and it is not accessible. However, this does work well for the “when called from JS as..” puzzle because those functions are published to the ExternalInterface.

I can use this technique if I make a wrapper for each of my procedure puzzles. The wrapper is a “when called from JS as..” puzzle and it calls the procedure puzzle (see screenshot). This is a little ugly, but it does work. If there is a way to access the ordinary procedure puzzles from the ExternalInterface we could avoid this two-step.

…and I used a JSON string argument to deal with the variable quantity of arguments that scalare mentioned in his post.

GLiFTeK wrote:

would this be used in a Time “every frame do” puzzle or a Loops “repeat while” puzzle so that the if then is “waiting” for the “procedure” variable to change to something acceptable?

Yes, you can possibly use that if-else structure inside every frame puzzle, because it is asynchronous. However, this would likely produce an infinite loop with repeat while, which is not.