David
Be careful that you do not save that file back to the same location.
The safest thing to do is open the script manager then press
control+shift+d to open the default script file.
When you save and compile it will save to your user setting folder and
leave the all user default file untouched.
This way if you break something that you cannot put right you only have
to delete the default files from your user settings folder and you will
have full functionality returned.
Overwrite the all users file by mistake and break something then you are
reinstalling jaws to get it back.
Bob
On 27/04/2012 12:59, David Ferrin wrote:
I found this file under explore shared settings, the path is as follows:
C:\Documents and Settings\All Users\Application Data\Freedom
Scientific\JAWS\13.0\Settings\enu
David Ferrin
Many people think they are generous because they give out free advice.
----- Original Message -----
From: Eric Damery
To: David Ferrin (d...@jaws-users.com)
Sent: Friday, April 27, 2012 6:02 AM
Subject: Here is the information I promised about adding to default script files
Hi David,
In the event you are just adding to your defaults rather than modifying our
scripts, this could be helpful avoiding problems in the future.
Regards,
Eric
Safely Adding Default Scripts
Starting with JAWS 12, the default script file makes use of MyExtensions.jsb.
MyExtensions.jss includes standard headers, but contains only a couple of stub
functions for source code. The purpose of the MyExtensions scripts is to
include in the JAWS distribution a script source file that will never contain
any Freedom Scientific source code, thus allowing the end user to safely add
new custom scripts without the need to make any changes due to a JAWS update.
For this reason, new scripts and functions added to MyExtensions and placed in
the user settings folder is a safe way to add custom scripts to JAWS.
You should be aware, however, that MyExtensions should not be used to overwrite
existing scripts or functions. Default scripts and functions do not call down
to MyExtensions, so any scripts or functions in MyExtensions that have the same
name as those in default or application scripts will never run. Scripts or
functions with unique names will run, which is why you can use MyExtensions for
added scripts and functions.
Because JAWS key map (JKM) files are layered, you can also assign key mappings
to your added MyExtensions scripts in default.jkm in your user settings. You
can use Keyboard Manager to locate your scripts in MyExtensions by looking
under Default scripts and assign keys to your custom scripts.
By adding your custom scripts to MyExtensions, and assigning keys in default,
you can safely extend JAWS scripts to include your own custom scripts. If you
have developed a library of custom functions in a JSB file, you can add it to
MyExtensions through the Use statement and it will now be available to you.
Just remember to use unique names for scripts or functions added through
MyExtensions, and save your modified MyExtensions source and compiled files to
your user settings, and you should be able to enjoy your own custom scripts
added to JAWS without having to make changes due to JAWS updates. You can also
copy your MyExtensions files to new versions of JAWS. Depending on the extent
of your script coding, you may want to ensure that your scripts are up-to-date
with the latest script innovations, but you won't need to modify your scripts
simply because JAWS updated.
For answers to frequently asked questions about this list visit:
http://www.jaws-users.com/help/
For answers to frequently asked questions about this list visit:
http://www.jaws-users.com/help/
