You add the .jsb file so it is Use "myFile.jsb" I should have added that the one feature this does not support is key mapping. So either way you do it you have to have one internet explorer jkm file with all of the keystrokes. So I suspect if you have not done this your scripts are not being called because there are not key bindings being loaded for them yet. I find it a bit of an inconvenient oversight and it'd definitely make the use statement even more powerful if .jkm was loaded to. What can we do. -----Original Message----- From: jawsscripts-bounce@xxxxxxxxxxxxx [mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Tom Shults Sent: Friday, May 24, 2013 12:37 PM To: jawsscripts@xxxxxxxxxxxxx Subject: [jawsscripts] Re: Extending functionality to JFW installed scripts Thanks Travis for this suggestion. I tried the "use" statement with great excitement, but it seemed that the keys assigned to my scripts were not imported to the Internet Explorer script. Maybe they should have been, and I did something wrong. The scripts I have added to Internet Explorer all perform custom navigation commands on some particular web pages I use frequently. There are 5 scripts, and each is assigned to keys unused by the default Explorer script. Each time I receive a new release of Jaws, I copy my custom scripts to the new default Explorer script. It does not really take that long, but I wish I could avoid having to go and manually edit the descriptions and key assignment for each script. If anyone has a suggestion how I can simplify importing the scripts, please let me know. Maybe the "use" command should have worked, and I screwed it up. Many thanks, Tom ----- Original Message ----- From: "Travis Roth" <travis@xxxxxxxxxxxxxx> To: <jawsscripts@xxxxxxxxxxxxx> Sent: Friday, May 24, 2013 5:19 AM Subject: [jawsscripts] Re: Extending functionality to JFW installed scripts You can compile your scripts into their own files and then add a "use" line to the internet explorer default scripts and recompile. Or do this in reverse, rename the shipping IE scripts to something else, name your scripts to the same as the original default scripts, and have your scripts use the "use" statement to call the renamed scripts. Then recompile this code with each version release. It depends on if you are overriding any default scripts which order. If your scripts are not overriding any default functionality then it should not matter what order you do it. -----Original Message----- From: jawsscripts-bounce@xxxxxxxxxxxxx [mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Tom Shults Sent: Friday, May 24, 2013 12:42 AM To: jawsscripts@xxxxxxxxxxxxx Subject: [jawsscripts] Extending functionality to JFW installed scripts All, Excuse the naivete of my question, as I have limited knowledge about Jaws scripting. I long ago added some additional functions to the script files FS delivers for Internet Explorer. Each time I update IE, or JFW, I manually re-add these functions to the FS scripts file, and recompile them. Is there a more prefered way of doing this, rather than using my manual method? Perhaps there is some include method or merge method I should be using? Thanks in advance for any pointers, Tom __________� View the list's information and change your settings at //www.freelists.org/list/jawsscripts __________� View the list's information and change your settings at //www.freelists.org/list/jawsscripts __________� View the list's information and change your settings at //www.freelists.org/list/jawsscripts __________� View the list's information and change your settings at //www.freelists.org/list/jawsscripts