[audacity4blind] Re: JAWS Script for Audacity-- new beta (2.1.0-beta.5)

  • From: Gary Campbell <campg2003@xxxxxxxxx>
  • To: audacity4blind@xxxxxxxxxxxxx
  • Date: Tue, 1 Mar 2016 10:50:52 -0700

Hi David,
What I mean is did every occurrence of wxWindowClass change to wxWindow, or only some of them. In other words, is it safe to change the value of the constant, or do I need to special-case that test? If they didn't all change then I run the risk of falsely recognizing another situation if I change the constant. Actually, it may not matter-- the bigger concern is if there are other places that used to be wxWindow. I'll just have to look at it instead of just changing it.


On 3/1/2016 2:22 AM, David Bailes wrote:

Hi Gary,
I've had a quick look at other class names, and the only other one that I've spotted that has changed is that for custom controls, the class name has changed from wxWindowClassNR to wxWindowNR. There are many custom controls in audacity, for example the buttons in the toolbars, track table, the time controls etc. If there any specific controls that you want me to check, just let me know,


On Tuesday, 1 March 2016, 6:18, Gary Campbell <campg2003@xxxxxxxxx> wrote:

THANK YOU!!! Do you know if that is an across the board change? or just in that specific instance?


On 2/29/2016 1:19 PM, David Bailes wrote:
Hi Gary,
concerning ctrl+tab saying grabber. It looks like the reason for this is that in 2.1.2 the class name of the grabber is wxWindow, whereas it was wxWindowClass in previous versions.


On Sunday, 28 February 2016, 3:47, Gary Campbell <campg2003@xxxxxxxxx> <mailto:campg2003@xxxxxxxxx> wrote:

Hi all,

I have just posted a new beta release (2.1.0-beta.5) of the JAWS script for Audacity.

Changes since rel2.1.0-beta3:

  * The check for existing scripts now ignores .jcf file so saved
    settings do not trigger the warning.
  * The check for an existing installation has been moved to after
    the Versions/Languages selection screen.  This allows the
    current/all users choice before checking for an existing
  * The radio buttons on the Select Versions/Languages page control
    both where the scripts are installed and the folder where the
    uninstaller and other supporting files are placed.
* The installer can now install for all users or the current user. (For all user installs the uninstaller and supporting files are
    stored in %programfiles% as before.  For current user installs
    they are placed in %localappdata%.)  If the user has higher than
    standard user privileges a command line option allows forcing
    installation for the current user.  (Fixes issue #3.)
  * The installer can now install into the shared scripts folder of
    JAWS 17.0.
  * For standard user installs the Install for current user or all
    users radio buttons on the Versions/Languages selection page do
    not appear.
  * SayLine, SayPriorLine, and SayNextLine now report no project if
    there are no tracks in the project. (fixes issue #1)

Known issues with this release:
In toolbars CTRL+TAB says "grabber".  (Issue #4)

You can download the 2.1.0-beta.5 installer here <https://github.com/campg2j003/JAWS-Script-for-Audacity/releases/download/rel2.1.0-beta.5/Jaws-Script-for-Audacity_2_1_0_beta5.exe>.

You can view the latest README <https://github.com/campg2j003/JAWS-Script-for-Audacity/blob/installer_ml/readme.md>. (This may be newer than the one in the beta 5 release.)

Let me know how it works for you.



Other related posts: