Hi Gary,
focus doesn't move,
David.
On Friday, 5 February 2016, 17:17, Gary Campbell <campg2003@xxxxxxxxx> wrote:
So it prompts for a number-- and then what? No movement? Move to the
wrong place?
Gary
On 2/5/2016 3:35 AM, David Bailes wrote:
Hi Gary,
Re track movement. It prompts for a number. I've also tried with Audacity
2.1.2, Jaws 17 and Windows 10, and Insert+A,g doesn't work for me.
David.
On Thursday, 4 February 2016, 16:46, Gary Campbell <campg2003@xxxxxxxxx>
wrote:
Re toolbar: I don't get it! It seems like focusing is working-- when
you tab between toolbars it doesn't hit the grabber. The code checks
for the window class of the grabber and skips it before setting focus.
I checked and the class name hasn't changed. I'll have to look at that
closer.
Re track movement. It works for me-- JAWS 17, Windows 10. I would ask
if the moveTrackUp/Down keys are assigned to CONTROL+Shift+Up/DownArrow,
but you say the GoToTrack command isn't working either. Does it prompt
for a number?
Garyy
On 2/1/2016 5:20 AM, David Bailes wrote:
Hi Gary,
I tested some of the script using Jaws 14, and Windows 7 64bit. I came
across a couple of issues:
1. The commands to to to a track by number or move the current track to a
track by number didn't do anything. (JAWSKey+a, g, and JAWSKey+a, m).
2. In the toolbars, pressing ctrl+tab causes Jaws to read grabber. I'm
pretty sure there's a keyboard focus issue with the grabber which is at the
start of each toolbar, and that it can be fixed for the next version of
Audacity.
David.
On Friday, 29 January 2016, 19:51, Gary Campbell <campg2003@xxxxxxxxx> wrote:
Hi all,
I have just posted a new beta release of the JAWS script for
Audacity. This release features installer changes for
multi-language support. Currently English and Spanish are
supported. Silence Preview has also been updated to support
Audacity 2.1.2.
I am particularly interested in feedback from people with
non-English JAWS installations, since I don't have access to such an
environment.
Please note that although the installer installs and compiles the
scripts into the selected language folders, the JAWS script compiler
always compiles the script files for the language of the
currently-running version of JAWS. Therefore, after installing you
will need to run JAWS with each of the other languages and compile
the scripts "manually". This is a kind of silly implementation but
it's the best I've come up with so far given the way the script
ompiler works. I am open to any suggestions!
The script has a new home. The script is now hosted on GitHub. You
can download the 2.1.0-beta3 installer here.
The installer exe for the current "official release" is also there (although
not the same binary file, it should have been built from the same source and
should be functionally equivalent).
You can view the latest README. (This may be newer than the one in the beta
3 release.)
Let me know how it works for you.
Thanks.
Gary
The audacity4blind web site is at
//www.freelists.org/webpage/audacity4blind
Subscribe and unsubscribe information, message archives,
Audacity keyboard commands, and more...
To unsubscribe from audacity4blind, send an email to
audacity4blind-request@xxxxxxxxxxxxx
with subject line
unsubscribe
The audacity4blind web site is at
//www.freelists.org/webpage/audacity4blind
Subscribe and unsubscribe information, message archives,
Audacity keyboard commands, and more...
To unsubscribe from audacity4blind, send an email to
audacity4blind-request@xxxxxxxxxxxxx
with subject line
unsubscribe
The audacity4blind web site is at
//www.freelists.org/webpage/audacity4blind
Subscribe and unsubscribe information, message archives,
Audacity keyboard commands, and more...
To unsubscribe from audacity4blind, send an email to
audacity4blind-request@xxxxxxxxxxxxx
with subject line
unsubscribe
