So, on line 1631 I put in a pause before we jump into the NavigateTrackPanel
function since I wasn't sure if the InputBox function would give focus back
to the track panel and NavigateTrackPanel assumes we have focus...
If InputBox(msgTrackNumber, msgGoToTrackTitle, s) Then
Pause()
NavigateTrackPanel (s, gsGoTrackUpKey, gsGoTrackDownKey)
Seems to work consistently after I do that!
Peace,
d
--------------------------------------------------
From: "David Engebretson Jr." <d.engebretson@xxxxxxxxxxx>
Sent: Saturday, February 06, 2016 7:28 PM
To: <audacity4blind@xxxxxxxxxxxxx>
Subject: [audacity4blind] Re: JAWS Script for Audacity-- new beta
(2.1.0-beta3)
So I uncommented the debug strings and heard the numbers... no matter what track I started on iStart and iNum always spoke as 0.
In this case I had 5 tracks, pressed JAWSKey+a, 'g' with focus on track 2, entered a value of 1 and it moved down to track 3. All other entries did not move focus (go to the desired track).
I'll have to revisit this tomorrow... mind boggling.
Peace,
d
--------------------------------------------------
From: "Gary Campbell" <campg2003@xxxxxxxxx>
Sent: Saturday, February 06, 2016 4:42 PM
To: <audacity4blind@xxxxxxxxxxxxx>
Subject: [audacity4blind] Re: JAWS Script for Audacity-- new beta (2.1.0-beta3)
Did you try changing the number after the %? Or comment out (place a ; at the start of the line) the if line and the endif line. I don't know what delay(-1) does, but I think it's an error. What's going on here is that we use TypeKey to send uparrow or downarrow to change tracks, and we delay to give the system tile to execute the keystroke. I don't understand why more delay doesn't fix it. I used 50 (or more) tracks to stress it thinking that moving more tracks would be more likely to skip a move and end up on the wrong track. Maybe try moving by just 1 track and see if that works. That should be the equivalent of 1 uparrow or downarrow.
You could try removing the ; before the SayString at line 1591 (the second one that says iNum, iStart, and iMax). iNum is the number of tracks (plus for down-- higher track numbers, minus for up). iMax should be the total number of tracks and iStart should be the track number you start on. I think they are 1-based numbers but I don't remember for sure.
You could try commenting the Let gfSilence lines-- one before the While and one a bit after the EndWhile). gfSilence is a flag that makes SayNonhighlightedText and some other things not speak. Then it should speak each track as it goes over it just as if you were moving manually. You could then try putting SayString(sKey) just before or after the TypeKey. It should say either UpArrow or DownArrow for each track to move. If it doesn't do that I'll have to figure out something else to try. Hopefully you can get the value of iNum and see if it makes sense. If the value of iNum is right and it isn't sending keystrokes, then try dropping something and see if it goes down :-).
If we can determine that it is going through the loop it should be sending the keys, and if it is doing that, I don't get why it doesn't move, particularly with, say delay(2) or 3. 5 would be half a sec between keystrokes and you can do that by hand.
If we aren't getting the right numbers for iStart and iMax then maybe we have to mess with the MSAA mode, but that seems like grasping at straws.
Is it working for anyone besides me?
Should we take this off list. (I kept it here in hopes that David B. and/or someone else would also try these.)
Gotta go peel potatoes before Nancy wakes up!
Gary
On 2/6/2016 3:03 PM, David Engebretson Jr. wrote:
I tried to change up the delay time with no apparent change in behaviour.
One thing I did notice is that, when a negative number is entered, there is movement of focus. Not necessarily the movement I would expect, but movement nonetheless. No movement if a positive number is entered.
Testing with XP and J15, Win7 and Win10 with J17.
I'm testing with 4 or 5 tracks, not 50 as you suggested in a previous post.
Thanks,
d
--------------------------------------------------
From: "Gary Campbell" <campg2003@xxxxxxxxx>
Sent: Saturday, February 06, 2016 9:18 AM
To: <audacity4blind@xxxxxxxxxxxxx>
Subject: [audacity4blind] Re: JAWS Script for Audacity-- new beta (2.1.0-beta3)
Hi Davids,
If you're willing to hack the script for a test, open audacity.jss in Script Mangler (JAWSKey+0) and go to function NavigateTrackPanel. Around line 1609 (CTRL+g to go to a line) you will find this code:
If iCount % 3 == 0 Then
delay(1)
EndIf
First, in the line If iCount % 3 == 0 Then, decrease the 3 and see what happens. (What that does is cause a delay every third keystroke.) Or increase the 1 in delay(1). (That delays .1 second.) See if one of those makes it work, and let me know the values. Of course, the more delay, the slower it executes. Just to avoid potential future confusion, go to the version constant (Const CS_SCRIPT_VERSION) around line 7 and update the date and time so it's clear that it's not the original version. Then press CTRL+s. Since you didn't make any errors, it will compile.
Oh, you might have wanted to make a backup of the file before you started-- too late now!
Thanks.
Gary
On 2/5/2016 10:43 AM, David Bailes wrote:
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,The audacity4blind web site is at
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
//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
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
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
