[audacity4blind] Re: Test script for Silence Preview
- From: "Dang Manh Cuong" <dangmanhcuong@xxxxxxxxx>
- To: <audacity4blind@xxxxxxxxxxxxx>
- Date: Fri, 28 Nov 2014 08:41:44 +0700
Hi all
By the way, I wrote a script to prevent jaws saying record when pressing the
R key, and Gary commented that we should allow user to choose to announce
that messsage if they prefer. So I'd like to ask for your oppinion. If you
like, I could write the script for you to turn on/ off the message when
pressing record.
Thanks to all.
Cuong
----- Original Message -----
From: "Gary Campbell" <campg2003@xxxxxxxxx>
To: <audacity4blind@xxxxxxxxxxxxx>
Sent: Friday, November 28, 2014 8:24 AM
Subject: [audacity4blind] Test script for Silence Preview
Hi,
Attached is a test version of the JAWS Scripts for Audacity that
implements silencing of speech during preview.
The way I'm handling silencing the preview button seems a bit risky to
me. I have observed that when the Preview button is activated the
dialog is destroyed, focus moves to the Audacity main window, and a
dialog for handling the preview is created. In order to detect when the
Preview button is activated, I watch for the focus to move to the main
window. JAWS DialogActive() function returns false, so I can't even
restrict this test to a dialog. When I detect this condition I set some
flags that suppress speech during focus changes. I think the next thing
that happens is that focus moves to the Stop button. I remember this
window handle and terminate Preview processing when this control is
destroyed. This means that any time focus moves to the Audacity main
window, from anywhere, the Preview functionality is activated. I
haven't noticed any problems with this in my usage over the past few
months, but my usage patterns tend to be quite repetitive. This is a
tricky change, and I'm not quite sure I understand my notes about it, or
actually just what the state of my development source is, which is a
very good way to introduce major problems into a project! I will release
a test version when I figure out just what files have changed, and how
to adequately label the version so we'll be able to recognize it easily
if someone somehow gets hold of it and reports a problem.
Oh well, attached are the files straight from my JAWS script folder. If
you'd like to test them, first back up your current script files. Then
save these files in your script folder and compile them with the Script
Manager. You might also back up PersonalizedSettings\Audacity.jsi. I
don't remember if the settings file has changed or not, or if it would
cause problems with the old version if it did.
Here are the additions to What's new.txt since the 2.0 release. Notice
that the silence preview hasn't even made it into it yet.
(This file last updated 7/25/2014)
. The URL for the JAWS User's Guide can now be updated via the script
(Control+Shift+j).
. Added support for the QuickSettings dialog (JAWS 13 and later).
. Made messages for moving and selecting more consistent.
New in V2.0 (9/15/2013):
....
Thanks.
Gary
-------------- Dang Manh Cuong The Assistive technology specialist Sao Mai
Vocational and assistive center for the blind 74/17 Bui Quang La, ward 12,
Go Vap Dst, HCMC, Vietnam Tel: +84862573309 E-mail:
trungtamsaomai2001@xxxxxxxxx saomai.congnghe@xxxxxxxxx Facebook:
https://www.facebook.com/SaoMaiCenter Website: http://www.saomaicente
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
Other related posts:
