Replies: 1 comment 3 replies
-
Hmm... It's definitely doable as a fallback in My recommendation would be to explicitly bind via BindGlobal: Dim vFunc:
For each vFunc in Array("ttest","otherMacro","whatever")
Call stdLambda.BindGlobal(vFunc, stdCallback.CreateFromModule("MyModule", vFunc))
next
Call stdLambda.Create("ttest(1)").Run() And you can absolutely loop through the functions in your project and add them in this way. Edit: For what it's worth I do just this in my spreadsheet extractor example by:
If you want it to be automated you could simply bind to vbInvoke |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Instead of doing: "application.run("testt", 1)" how about doing this instead: "testt(1)"
Basically an intepreter that can recognize a defined public procedure somewhere in the project?
It could either just try to run the command and see if something works or through the mentioned intepreter.
I have something like this as an expansion of stdlambda.
Beta Was this translation helpful? Give feedback.
All reactions