I think that that left bracket and right bracket messages should be
controlled by Announce Audacity messages, as I think they fall into the
"might well be annoying" category.
On 12 March 2018 at 16:36, Gary Campbell <campg2003@xxxxxxxxx> wrote:
Well, it wasn't working because of a missing else.
The Announce Audacity Messages (which as I think about it could use a
better name) tries to allow you to silence script-generated messages that
might be annoying after a while. The Announce Position option is intended
to let you choose whether or not to hear the position with cursor motion
keys like arrows. So my question is about [ and ]. Should they be
considered a position announcement even though they aren't related to
motion, or as an Audacity script message controlled by Announce Messages?
On 3/10/2018 7:24 AM, David Bailes wrote:
I find these Audacity settings confusing. The announce Audacity toolbars
setting is independent of the Announce audacity messages setting. But for
both Announce position and preview motion, checking them only has any
effect if Announce audacity messages is checked.
Also Jawskey+p is meant to "temporarily toggle between speaking the
position and playing audio" but does not do so.
On 9 March 2018 at 20:00, Gary Campbell <campg2003@xxxxxxxxx> wrote:
Thanks for testing! Is Announce Audacity Messages on? Maybe cursor
motion should not be controlled by Announce Messages any more since it now
has its own option. I can't remember right now what it would take to
change that. I had all the speech going through a single path so that I
wouldn't miss any messages :-).
On 3/6/2018 7:12 AM, David Bailes wrote:
I've just done some testing of your script, and the only problem I've
found so far is the the two options announce position and preview motion
don't seem to have any effect. That is, if the focus is a track and I move
the cursor using, for example, left/right arrow, then nothing is spoken or
played. I'm using windows 10 1709, and Jaws 2018.1802.78.
Apart from that, the script works well, and I thought that the readme was
very well written,
On 2 March 2018 at 22:18, Gary Campbell <campg2003@xxxxxxxxx> wrote:
I just posted a new release candidate of the script. The installer is
The source is on the next
It is intended that this will become the 2.2.0 release (except for an
update to the German README) in a week or so if there aren't problem
New in this release:
-If we can't get the position field via GetWindowText we try to get it
with MSAA. This doesn't get the letters and period, but it does get
something when we used to get an error.
- You can now choose to compile scripts with either JAWSUtil.vbs
(default), scompile directly, or not to compile at all. To not use
JAWSUtil.vbs, on the installer command line, include the /compile=s
switch. /compile=n will suppress compilation of scripts.
- Keys to move current track to marked track and exchange current track
with marked track now remain in the Audacity key layer. This allows moving
several consecutive tracks more easily.
- Added JAWSKey+a&SPACE as an alias for JAWS+a&k (mark current track).
- Changed copyright (in message in audacity.jss and installer) to 2018.
This works with Audacity 2.2.2-rc.1 release.
The following has not been tested and needs to be:
- Install to shared scripts.
- Install via non-admin account.
- Just Scripts install.
- Probably more corner cases with installs.
Any help with this would be greatly appreciated.
I'm still looking for someone that can tell me how a compile with JAWS