Re: [Audacity-quality] bug 334 (was Re: Testing of windows RC - Please describe your usual workflow!)

[Bill W. <bi...@go...>]

On 20/02/2012, at 6:18 PM, Vaughan Johnson wrote:

> On 2/16/2012 8:10 AM, Bill Wharrie wrote:
>> 
>> On 16/02/2012, at 10:00 AM, James Crook wrote:
>> 
>> [snip]
>>> 
>> 
>> 334 still exists and is release noted.
> 
> My impression is that the fixes made so far have fixed most of the
> related bugs in this entry. Is that right? Can it be demoted?

The bug as described in the title still exists. The steps to reproduce should probably be changed to reflect that - they currently describe the non-modal nature of effect progress dialogs which has been fixed. The release notes correctly describe the bug.

Also note in comment 22
http://bugzilla.audacityteam.org/show_bug.cgi?id=334#c22
that Leland says he can reproduce the bug on Windows.

It is currently P3. I may be the only one who has encountered it! I'm impatient, and my habit was to "Save Project" then click the window close button as soon as the "saving …" dialog goes away. I've learned not to do that, and now "patiently" wait for the "inspecting project data" dialog to come and go. 

That said, I think it still rates a P3 since there is a situation (described in the release notes) where the project is destroyed.

-- Bill