Re: [Audacity-devel] Checklist - Menus active during Export + JAWS

[David R. S. <dav...@sh...>]

James,

Three comments from one screen reader user listen-point.

I _do not_ like all the babble from my screen reader!! I try to shut off 
the dialogue but it just keeps coming! If I want to know the progress of 
an effect for example, I check the screen, the second (third?) line from 
the bottom gives time remaining.

Regarding generate, two comments here - no I don't want a progress report 
either. More babble. If i want to know that something is finished in 
Audacity, simply pressing the alt button will tell me - if it says 'system 
menu' I know things are still in progress. if it says 'file menu' I know 
it's finished.

The second item about generate menu - in 1.3.3 it's somewhat annoying that 
items are marked with the first letter for quick navigation. since i write 
nyquist plug-ins which I want to test, I often want to use my Nyquist 
Generate prompt. But pressing 'n' always takes me into Noise, instead of 
cycling me through everything that starts with 'n'. So I'm still using 
1.2.4 the majority of the time just for this reason.

Overall though I _love_ using 1.3.3! If I'm not testing my plug-ins, this 
is my choice!!

thanks

David

-- 
David R. Sky
http://www.shellworld.net/~davidsky/


On Tue, 24 Jul 2007, James Crook wrote:

> The problem that the menu is still active whilst some lengthy action
> like 'Export' is in progress is a thorny one, and down to a complex
> change in the progress dialogs.  That change is made to accommodate
> screen readers which need to have the progress dialog around even after
> it has closed.
>
> It used to be that progress dialogs stole the message loop, like
> ShowModal does, so nothing else could happen other than screen refresh
> and clicking cancel on the dialog.   I did try a trick to recreate that
> behaviour using apptraits to disable the menu, but that only disables
> the menu.  Other activities like selecting audio and playing and
> recording audio are still possible - and these may reenable the menus!
>
> Leland, can you comment on this?  I've left the new experimental code to
> disable menus etc commented out in AudacityProject::ProgressShow and
> ProgressHide; two different attempts, one using apptraits, one using
> different arguments to wxSafeYield.
>
> One route forward is to lock down all the different behaviours - but
> that looks messy.  I'm actually a little puzzled as to why the changed
> SafeYield didn't work - it's as if there is another SafeYield somewhere
> else that yields to more...  If the messy way is the only way, then we
> can do it, but I'd like to see if there is an alternative first.
>
> On a related issue...  Generate doesn't have a progress dialog, and I
> think it should.  Do people agree?
>
> --James.
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Audacity-devel mailing list
> Aud...@li...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>