I did not mean to dismiss the scripting engine so curtly. In all honesty I'm just not familiar with or comfortable with BASIC, and the first time I tried exploring the scripting help documentation you have it was not very "beginner friendly" (double checking now, it looks like significant improvements have been made to the documentation, though it could probably still use some work). Besides that, my "arcane" remark was more targeted at the specific issue/thread I linked of "how can I ShellExecute something with spaces in its path". Even one of this site's top tier members couldn't help. Though it's also possible that was a bug with KBPro 2017 (I'm now using 2020); I haven't tried again since

Which part of my message are you referring to when you say "locking up"? I'm not sure locking up is quite the right word for it. It's more like, under some circumstances (EX: when changing dictation sources or otherwise reloading the user profile), commands like "backspace <number>" will stop working. It doesn't seem to affect all commands, rather primarily affecting those with some form of variable in the name. If you would like, I can try to describe more specific reproduction steps.

“Talk is cheap. Show me the code.” ~ Linus Torvalds

"It is good to have empathy.  But it is not essential.  What is essential is that one displays empathy, however one musters it." ~ ax (in a post on this very forums)

more favorite quotes