On Wed, Nov 28, 2018 at 09:00 AM, JM Casey wrote:
The scripts would be loaded at program startup, I believe, not JAWS startup. I think it’s quite picky about it as well; in order for the scripts to load automatically they have to share the same name as the programme’s main executable.Even with my limited knowledge I do know that your statement about a script loading when a program starts up is correct. I had always wondered what the mechanism was for JAWS to be able to associate a script with a program, and based on what I saw yesterday your statement regarding a match between the JSS file prefix and the EXE file prefix makes perfect sense. I'm sure someone else can verify.
I'm not the moderator, but I certainly hope this conversation will be permitted to continue. There can be nothing more JAWS specific than how to tailor it to work with third party programs for which the existing JAWS configuration, sans scripts, simply does not work. Even the casual JAWS user benefits by having some idea of the mechanisms needed to make certain "not off the shelf" programs accessible (or more accessible), even if they can't actually write scripts themselves.
Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763
Explanations exist; they have existed for all time; there is always a well-known solution to every human problem — neat, plausible, and wrong.
~ H.L. Mencken, AKA The Sage of Baltimore