[typeabilitybeta] Re: Two TypeAbility problems
- From: "Brian Hartgen" <Brian.Hartgen@xxxxxxxxxxxxxxxxxxxxx>
- To: <typeabilitybeta@xxxxxxxxxxxxx>
- Date: Thu, 7 May 2009 17:06:57 +0100
I forgot to give the other problem.
Basically, we are still having this problem with jaws 10 where bringing
any of the lists into view causes the speech rate to change to that
which you have set within jaws.
Brian Hartgen
Product Development Manager
Freedom Scientific approved script writer
Dolphin Computer Access approved script writer
T&T Consultancy Ltd
Advantage House
Trentham Business Quarter
Bellringer Road
Trentham
Stoke-On-Trent
ST4 8GB
Tel: 01782 644141
Fax: 01782 645135
Web Site, www.tandt-consultancy.com
NOTICE: The information contained in this email and any attachments is
confidential and may be legally privileged. If you are not the intended
recipient you are hereby notified that you must not use, disclose,
distribute, copy, print or rely on this e-mail's content. If you are not
the intended recipient, please notify the sender immediately and then
delete the email and any attachments from your system. T&T Consultancy
Ltd have made strenuous efforts to ensure that emails and any
attachments generated by its staff are free from viruses. However, it
cannot accept any responsibility for any viruses which are transmitted.
We therefore recommend you scan all received e-mail messages.
Registered in England No. 4098268
-----Original Message-----
From: typeabilitybeta-bounce@xxxxxxxxxxxxx
[mailto:typeabilitybeta-bounce@xxxxxxxxxxxxx] On Behalf Of Brian Hartgen
Sent: Thursday, 7 May 2009 5:04 PM
To: typeabilitybeta@xxxxxxxxxxxxx
Subject: [typeabilitybeta] Two TypeAbility problems
Hi
I have no idea if this list is still active, but one of our customers
has alerted us to a TypeAbility problem.
He is using the latest build of TypeAbility with jaws 10 and MAGic 11.
When both are running together, and when progressing through lesson 61,
pressing the right shift plus F causes jaws to announce "No, it's not
the right shift plus F, it's the right shift plus F, that's F as in
Frank". I have verified this and it happens on my computers also.
Thank you.
Brian Hartgen
Product Development Manager
Freedom Scientific approved script writer
Dolphin Computer Access approved script writer
T&T Consultancy Ltd
Advantage House
Trentham Business Quarter
Bellringer Road
Trentham
Stoke-On-Trent
ST4 8GB
Tel: 01782 644141
Fax: 01782 645135
Web Site, www.tandt-consultancy.com
NOTICE: The information contained in this email and any attachments is
confidential and may be legally privileged. If you are not the intended
recipient you are hereby notified that you must not use, disclose,
distribute, copy, print or rely on this e-mail's content. If you are not
the intended recipient, please notify the sender immediately and then
delete the email and any attachments from your system. T&T Consultancy
Ltd have made strenuous efforts to ensure that emails and any
attachments generated by its staff are free from viruses. However, it
cannot accept any responsibility for any viruses which are transmitted.
We therefore recommend you scan all received e-mail messages.
Registered in England No. 4098268
-----Original Message-----
From: typeabilitybeta-bounce@xxxxxxxxxxxxx
[mailto:typeabilitybeta-bounce@xxxxxxxxxxxxx] On Behalf Of David Pinto
Sent: Wednesday, 24 September 2008 2:25 PM
To: typeabilitybeta@xxxxxxxxxxxxx
Subject: [typeabilitybeta] TypeAbility 3.0.30 ready for download
TypeAbility 3.0.30 is ready for download. This build has been devoted to
2
things.
1. Sometimes when TypeAbility was opened, the sign in screen didn't pop
up.
This has been solved, by putting a refresh in the AutoStartEvent.
2. TA was interfering with the users default voice settings when you're
not
in the TypeAbility worksheet. This has been solved by a scheme that is
outlined at the bottom of this document.
Please test out the following.
1. Test key repeat being off in TypeAbility, but not off otherwise. When
in
TypeAbility, hold down a key, it should not keep typing. Then
close TypeAbility, and in another rtf document, hold down a key, it
should
keep typing till you let go.
2. Just for testing purposes, In the JAWS individual voice adjustment
dialog, Set your PC voice rate to
very fast, and its pitch to very low. Then sign in to TypeAbility and
note
whether TypeAbility speaks as it normally does. Then ALT TAB to another
application, and note whether TypeAbility speaks with your fast rate and
low
pitch.
3. Basically, test out TypeAbility in ways in which you felt it
interfered
with your voice settings outside of TypeAbility.
Thanks. Now the following are the details on the new scheme that has
made
the above
possible.
1. Basically, there are only 5 settings that TypeAbility needs to be
written
to the Wordpad.jcf file. But in previous builds of TypeAbility,
TypeAbility
installed a wordpad.jcf file that contained lots of unnecessary
settings,
some of which may not have respected the user's default settings and
permanently over wrote them for Wordpad. Although most users have MS
word,
and by default, files with extensions of .rtf are opened in MSWord, some
users either do not have MS Word, or they've changed their file
associations, so that RTF files always open in Wordpad, rather than
MSWord.
In that instance, TypeAbility's JCF settings were not respecting the
user's
desires.
2. Now, when TypeAbility opens, it looks in the wordpad.jcf file for the
settings that TypeAbility needs to adjust. If it doesn't find those
settings
there, it looks in the Default.jcf file. It then stores those values in
variables, so that those values can be restored when TypeAbility is
closed.
Note that the settings are actually restored in the Wordpad.jcf file,
regardless of whether there was initially a Wordpad.jcf file or not. In
the
latter case, the Wordpad.jcf settings will be the same as the
Default.jcf
settings.
3. Although it is not optimum, when TypeAbility is installed, a blank
Wordpad.JCF file is loaded. This is necessary because previous versions
of
TypeAbility always loaded a wordpad.jcf file that did not respect the
user's
settings. So to remedy this, the wordpad.jcf file has to be nulled. So,
if
before installing TypeAbility, the user had made changes to wordpad's
JAWS
settings, then those settings in the Wordpad.jcf file will be lost.
Although
this is not desirable, note that if the user subsequently changes the
Wordpad.jcf settings, they will not be permanently overwritten by
TypeAbility. They will only be overwritten during fresh installs of
TypeAbility. The above scheme will ensure that as much as possible, the
user's default settings will be respected in Non TypeAbility wordpad
documents.
4. Now, when TypeAbility is opened, the 5 settings that are temporarily
written to the Wordpad.jcf file are the following.
a. Key repeat is set to 0, so users who hold down a key too long, won't
be
repeatedly typing that key. This is important for beginning users, and
users
with nervous or muscular impairments.
b. Tutor Messages are set to 0. This is important so that when opening
TypeAbility dialogs, the user is not burdened with tutor information.
Also,
when the user accidentaly activates a menu by pressing the ALT key,
although
TypeAbility will automatically close the menu, JAWS will never the less
speak the tutor message for menus, unless tutor messages are turned of.
c. Access key is set to 0. the Access key setrting can make JAWS
announce
the hotkey for a dialog or menu item. It's important to silence this
message, so that when opening TypeAbility dialogs, or accidentally
activating a menu, the user is not burdened with the access key
information.
d. Help Balloon is set to 0. This is important so that if the JAWS
cursor is
on a a control with a help balloon, JAWS won't speak it.
e. Smart help is set to 0.
5. As stated earlier, when TypeAbility is closed, then in the
Wordpad.jcf
file, those 5 settings are restored to the user's original settings.
Also
note that other TypeAbility settings, such as speech rate, pitch,
volume,
punctuation, key Interrupt, and Typing echo, do not need to be written
to
the Wordpad.jcf file, because JAWS can adjust them on the fly. And those
settings are also restored to the user's settings, when the user is not
in
TypeAbility.
David
Other related posts:
