1.3.5 rc1 effect dialogs go modeless

14 Messages Forum Options Options
Alert me of new posts
Permalink
David Bailes-2
1.3.5 rc1 effect dialogs go modeless
Reply Threaded More
Print post
Permalink
Hi,

In an effects dialog, if you press preview, then the focus returns to
the dialog (bug fixed), but the dialog becomes modeless, so allowing
someone to do something in the main window (like deleting all the
tracks) before pressing the ok button (crash).

David.

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Vaughan Johnson
Re: 1.3.5 rc1 effect dialogs go modeless
Reply Threaded More
Print post
Permalink
David Bailes wrote:
> Hi,
>
> In an effects dialog, if you press preview, then the focus returns to
> the dialog (bug fixed), but the dialog becomes modeless, so allowing
> someone to do something in the main window (like deleting all the
> tracks) before pressing the ok button (crash).
>
>  

Really good catch, David!

I've debugged it to the extent of finding that it's not due to the
SetFocus() call. Instead, if you comment out line 424 of Effect.cpp:

         previewing = GetActiveProject()->ProgressUpdate(t);

...the modality problem does not happen. I haven't looked at OnPreview
in a long time, but with the original, where preview was only 3 seconds,
progress wasn't necessary, so I expect this code was added when a pref
was added to allow user-specified preview length.

Anyway, Leland is, I think, the threaded progress expert. Maybe it's the
call to SetEnabledWindow() at line 3593 of Project.cpp that's switching
the modality?

- Vaughan

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Leland (AudacityTeam)
Re: 1.3.5 rc1 effect dialogs go modeless
Reply Threaded More
Print post
Permalink


--On May 3, 2008 1:16:43 AM -0700 Vaughan Johnson
<vaughan@...> wrote:

>
> Anyway, Leland is, I think, the threaded progress expert. Maybe it's the
> call to SetEnabledWindow() at line 3593 of Project.cpp that's switching
> the modality?
>
I'd rephrase that a little...

"Leland is the threaded progress screwer upper."

I really need to redo/undo that stupid
"GetActiveProject()->ProgressUpdate(t)" thing.  That has a lot to do with
this whole losing modal mess.

Anyway, I'll take a look to see if there's a quick fix.  Otherwise, I may
attempt to revert to a standard (or closer to it) progress dialog for 1.3.6.

Leland


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Vaughan Johnson
Re: 1.3.5 rc1 effect dialogs go modeless
Reply Threaded More
Print post
Permalink
Leland wrote:

> --On May 3, 2008 1:16:43 AM -0700 Vaughan Johnson
> <vaughan@...> wrote:
>
>  
>> Anyway, Leland is, I think, the threaded progress expert. Maybe it's the
>> call to SetEnabledWindow() at line 3593 of Project.cpp that's switching
>> the modality?
>>
>>    
> I'd rephrase that a little...
>
>  

I've grown to hate the LOL abbreviation, but I did so at this, twice!

I'd have been afraid to even wade into that stuff, and maybe it screwed
up some things, but it fixed several others, AFAIR!

I'm sticking with "expert"! Thanks, Leland!

- V

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Martyn Shaw-2
Re: 1.3.5 rc1 effect dialogs go modeless
Reply Threaded More
Print post
Permalink
Yeah David, nice catch!

I think V is slightly off, but helpful anyway (to me at least).  I
think the problem is in AudacityProject::ProgressHide(), a few lines
up in Project.cpp to he indicates; the project window is getting
enabled when Preview finishes (and I assume that means it's children
as well), which isn't what we want in a effect.  We want the effect
dialog to be enabled (only).

I have a fix here which is 'better than we have' but not ideal (see
below).

For an effect (it would need doing for all) I've tried putting

void ExampleEffect::OnPreview(wxCommandEvent &event)
{
     TransferDataFromWindow();
-   m_pEffect->Preview();
+   m_pEffect->Preview(this);
     this->SetFocus();
}

following the logic that in order to enable the correct dialog,
Effect::Preview needs to know which one it is being called from.  Then
I followed this through with

-   void Effect::Preview()
+   void Effect::Preview(wxDialog * effectDialog)
...
-      GetActiveProject()->ProgressHide();
+      GetActiveProject()->ProgressHide(effectDialog);

and an overloaded (correct term?)

+void AudacityProject::ProgressHide(wxDialog * effectDialog)
+{
+   ProgressHide();   // enable project window
+   SetEnabledWindow( effectDialog );   // and then set to the effect
dialog again
+}

which enables the correct window again.

Why is it 'not ideal'?  I think there are (possibly) three progress
windows that can open when you do a preview (if it's long enough).
"Mix and Render", "Preparing preview" and the preview one.

If somebody cancels the "Preparing preview" progress dialog then
things carry on anyway (but they do already) without the effect.
Probably the same for the "Mix and Render" progress dialog but I've
ran out of brain, and time.

I could commit the changes above in a day or two if they'd be useful,
or maybe it's already fixed? (I see 66 unread emails in my inbox).

Martyn
Having an early night, due to a rugby tour for the last 2 days.  I'm
not entirely sure what happened.

Vaughan Johnson wrote:

> David Bailes wrote:
>> Hi,
>>
>> In an effects dialog, if you press preview, then the focus returns to
>> the dialog (bug fixed), but the dialog becomes modeless, so allowing
>> someone to do something in the main window (like deleting all the
>> tracks) before pressing the ok button (crash).
>>
>>  
>
> Really good catch, David!
>
> I've debugged it to the extent of finding that it's not due to the
> SetFocus() call. Instead, if you comment out line 424 of Effect.cpp:
>
>          previewing = GetActiveProject()->ProgressUpdate(t);
>
> ...the modality problem does not happen. I haven't looked at OnPreview
> in a long time, but with the original, where preview was only 3 seconds,
> progress wasn't necessary, so I expect this code was added when a pref
> was added to allow user-specified preview length.
>
> Anyway, Leland is, I think, the threaded progress expert. Maybe it's the
> call to SetEnabledWindow() at line 3593 of Project.cpp that's switching
> the modality?
>
> - Vaughan
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Audacity-devel mailing list
> Audacity-devel@...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Vaughan Johnson
Re: 1.3.5 rc1 effect dialogs go modeless
Reply Threaded More
Print post
Permalink
Thanks, Martyn. You're right about the real culprit.

I implemented the fix a little more OOP-ish:

    * Gave the Effect base class a variable for its dialog (if there is
      one). Already had one for its parent.
    * Then descendant Effects that create dialogs have them set it to
      the one each creates, e.g., at the end of the dialog's constructor:

        mEffect->SetDialog(this);


    * Also moved the SetFocus() call into Effect::Preview(), so it
      doesn't need to be duplicated in each descendant, and removed the
      SetFocus() from each descendant's ::OnPreview().
    * Then implemented your change for ProgressHide except rather than
      overload it, just declared the arg to have a default NULL and then
      SetEnabledWindow() on it only if non-NULL.
    *  >>" If somebody cancels the "Preparing preview" progress dialog then
      things carry on anyway (but they do already) without the effect.
      Probably the same for the "Mix and Render" progress dialog..."?>>

        Added the arg to both ProgressHide calls in Effect::Preview(). I
        think that handles the 'not ideal', because Mix-and-Render
        doesn't have a controls dialog, so it's okay to re-enable the
        Project window, right?




This involved 2-3 lines of changes in about 20 files. So the question is
whether to put all those changes into 1.3.5.

I posted a 1.3.5-rc4 Windows installer with these changes, built on
latest CVS (incl. locale updates), at
http://audacity.sourceforge.net/files/audacity-win-unicode-1.3.5-rc4.exe 
, but NOT committed these progress-vs-modality changes to CVS.

If there's time to test them on Windows, should we put them into 1.3.5?
If not, we can just build the release from CVS. If so, even if more
problems show up, we can probably fix by 1.3.6.

- Vaughan



Martyn Shaw wrote:

> Yeah David, nice catch!
>
> I think V is slightly off, but helpful anyway (to me at least).  I
> think the problem is in AudacityProject::ProgressHide(), a few lines
> up in Project.cpp to he indicates; the project window is getting
> enabled when Preview finishes (and I assume that means it's children
> as well), which isn't what we want in a effect.  We want the effect
> dialog to be enabled (only).
>
> I have a fix here which is 'better than we have' but not ideal (see
> below).
>
> For an effect (it would need doing for all) I've tried putting
>
> void ExampleEffect::OnPreview(wxCommandEvent &event)
> {
>      TransferDataFromWindow();
> -   m_pEffect->Preview();
> +   m_pEffect->Preview(this);
>      this->SetFocus();
> }
>
> following the logic that in order to enable the correct dialog,
> Effect::Preview needs to know which one it is being called from.  Then
> I followed this through with
>
> -   void Effect::Preview()
> +   void Effect::Preview(wxDialog * effectDialog)
> ...
> -      GetActiveProject()->ProgressHide();
> +      GetActiveProject()->ProgressHide(effectDialog);
>
> and an overloaded (correct term?)
>
> +void AudacityProject::ProgressHide(wxDialog * effectDialog)
> +{
> +   ProgressHide();   // enable project window
> +   SetEnabledWindow( effectDialog );   // and then set to the effect
> dialog again
> +}
>
> which enables the correct window again.
>
> Why is it 'not ideal'?  I think there are (possibly) three progress
> windows that can open when you do a preview (if it's long enough).
> "Mix and Render", "Preparing preview" and the preview one.
>
> If somebody cancels the "Preparing preview" progress dialog then
> things carry on anyway (but they do already) without the effect.
> Probably the same for the "Mix and Render" progress dialog but I've
> ran out of brain, and time.
>
> I could commit the changes above in a day or two if they'd be useful,
> or maybe it's already fixed? (I see 66 unread emails in my inbox).
>
> Martyn
> Having an early night, due to a rugby tour for the last 2 days.  I'm
> not entirely sure what happened.
>
> Vaughan Johnson wrote:
>  
>> David Bailes wrote:
>>    
>>> Hi,
>>>
>>> In an effects dialog, if you press preview, then the focus returns to
>>> the dialog (bug fixed), but the dialog becomes modeless, so allowing
>>> someone to do something in the main window (like deleting all the
>>> tracks) before pressing the ok button (crash).
>>>
>>>  
>>>      
>> Really good catch, David!
>>
>> I've debugged it to the extent of finding that it's not due to the
>> SetFocus() call. Instead, if you comment out line 424 of Effect.cpp:
>>
>>          previewing = GetActiveProject()->ProgressUpdate(t);
>>
>> ...the modality problem does not happen. I haven't looked at OnPreview
>> in a long time, but with the original, where preview was only 3 seconds,
>> progress wasn't necessary, so I expect this code was added when a pref
>> was added to allow user-specified preview length.
>>
>> Anyway, Leland is, I think, the threaded progress expert. Maybe it's the
>> call to SetEnabledWindow() at line 3593 of Project.cpp that's switching
>> the modality?
>>
>> - Vaughan
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
>> Don't miss this year's exciting event. There's still time to save $100.
>> Use priority code J8TL2D2.
>> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
>> _______________________________________________
>> Audacity-devel mailing list
>> Audacity-devel@...
>> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>>
>>    
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Audacity-devel mailing list
> Audacity-devel@...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>
>  

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Richard Ash (audacity-help)
Re: 1.3.5 rc1 effect dialogs go modeless
Reply Threaded More
Print post
Permalink
On Mon, 2008-05-05 at 00:26 -0700, Vaughan Johnson wrote:

> This involved 2-3 lines of changes in about 20 files. So the question is
> whether to put all those changes into 1.3.5.
>
> I posted a 1.3.5-rc4 Windows installer with these changes, built on
> latest CVS (incl. locale updates), at
> http://audacity.sourceforge.net/files/audacity-win-unicode-1.3.5-rc4.exe 
> , but NOT committed these progress-vs-modality changes to CVS.
>
> If there's time to test them on Windows, should we put them into 1.3.5?
> If not, we can just build the release from CVS. If so, even if more
> problems show up, we can probably fix by 1.3.6.

I've just tried running the exe under wine, and seems to work OK. I'd
vote to put them in before 1.3.5, so we have the minimum number of
complex changes (besides modularisation) between 1.3.5 and 1.3.6, so
it's clearer what the cause of any issues is.

Richard


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Gale Andrews
Re: 1.3.5 rc1 effect dialogs go modeless
Reply Threaded More
Print post
Permalink

| From Vaughan Johnson <vaughan@...>
| Mon, 05 May 2008 00:26:09 -0700
| Subject: [Audacity-devel] 1.3.5 rc1 effect dialogs go modeless

> I implemented the fix a little more OOP-ish:...
>         Added the arg to both ProgressHide calls in Effect::Preview(). I
>         think that handles the 'not ideal', because Mix-and-Render
>         doesn't have a controls dialog, so it's okay to re-enable the
>         Project window, right?
>
> This involved 2-3 lines of changes in about 20 files. So the question is
> whether to put all those changes into 1.3.5.
>
> I posted a 1.3.5-rc4 Windows installer with these changes, built on
> latest CVS (incl. locale updates), at
> http://audacity.sourceforge.net/files/audacity-win-unicode-1.3.5-rc4.exe 
> , but NOT committed these progress-vs-modality changes to CVS.
>
> If there's time to test them on Windows, should we put them into 1.3.5?
> If not, we can just build the release from CVS. If so, even if more
> problems show up, we can probably fix by 1.3.6.

I've tested RC4 with a number of effect dialogues and the dialogue remains
modeless after preview now. I also tried doing something in the main  
window when previewing, and when mixing and rendering and preparing
preview for a longer preview, and could not.

However there is a replicable problem now in Equalization (but not the
other effects I tried). If I preview the EQ effect, even a short preview
with only a "Previewing" dialogue, cancel it, then preview and cancel
the preview a second time, there is a crash. Tested with three different
files so the file is not the problem.

This scenario does not crash a recent CVS build without the current
modeless fix. So it does not look like this should be committed into
1.3.5, at least without a warning.      



Gale

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
David Bailes-2
Re: 1.3.5 rc1 effect dialogs go modeless
Reply Threaded More
Print post
Permalink
Hi,

On 5/5/08, Vaughan Johnson <vaughan@...> wrote:

> Thanks, Martyn. You're right about the real culprit.
>
> I implemented the fix a little more OOP-ish:
>
>     * Gave the Effect base class a variable for its dialog (if there is
>       one). Already had one for its parent.
>     * Then descendant Effects that create dialogs have them set it to
>       the one each creates, e.g., at the end of the dialog's constructor:
>
>         mEffect->SetDialog(this);
>
>
>     * Also moved the SetFocus() call into Effect::Preview(), so it
>       doesn't need to be duplicated in each descendant, and removed the
>       SetFocus() from each descendant's ::OnPreview().
>     * Then implemented your change for ProgressHide except rather than
>       overload it, just declared the arg to have a default NULL and then
>       SetEnabledWindow() on it only if non-NULL.
>     *  >>" If somebody cancels the "Preparing preview" progress dialog then
>       things carry on anyway (but they do already) without the effect.
>       Probably the same for the "Mix and Render" progress dialog..."?>>
>
>         Added the arg to both ProgressHide calls in Effect::Preview(). I
>         think that handles the 'not ideal', because Mix-and-Render
>         doesn't have a controls dialog, so it's okay to re-enable the
>         Project window, right?
>
>
>
>
> This involved 2-3 lines of changes in about 20 files. So the question is
> whether to put all those changes into 1.3.5.
>
> I posted a 1.3.5-rc4 Windows installer with these changes, built on
> latest CVS (incl. locale updates), at
> http://audacity.sourceforge.net/files/audacity-win-unicode-1.3.5-rc4.exe
> , but NOT committed these progress-vs-modality changes to CVS.
>
> If there's time to test them on Windows, should we put them into 1.3.5?
> If not, we can just build the release from CVS. If so, even if more
> problems show up, we can probably fix by 1.3.6.

On windows XP I tested that focus is returned to an effect dialog
after preview, and if you tracks->mic and render, then cancel the
progress window, focus is returned to the main window.

I found one problem. In Effects->Equalization, if you press preview
twice, audacity now crashes.

David.

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
David Bailes-2
Re: 1.3.5 rc1 effect dialogs go modeless
Reply Threaded More
Print post
Permalink
Snap!

David.

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Gale Andrews
Re: 1.3.5 rc1 effect dialogs go modeless
Reply Threaded More
Print post
Permalink

| From Gale Andrews <gale@...>
| Mon, 05 May 2008 18:31:55 +0100
| Subject: [Audacity-devel] 1.3.5 rc1 effect dialogs go modeless
> I've tested RC4 with a number of effect dialogues and the dialogue remains
> modeless after preview now.

Sorry, mixing my modes. To clarify, the basic fix works (the dialog
is *not* now modeless after preview), so you cannot do anything
in the main window. Win XP SP2.  


Gale




-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Vaughan Johnson
Re: 1.3.5 rc1 effect dialogs go modeless
Reply Threaded More
Print post
Permalink
Thanks, Gale & David for finding and pointing out the problem with
EffectEqualization. It's due to EffectEqualization::DontPromptUser(). My
fix involved making the Effect know about its dialog by having the
dialog call Effect::SetDialog() at the end of its constructor.

But in EffectEqualization, it creates TWO dialogs, the "real" one and a
temporary one in EffectEqualization::DontPromptUser() that's not shown,
and the temp was being set in the Effect::SetDialog() call, so when
trying to SetFocus at the end of Effect::Preview(), the temp was gone
and that pointer was bogus. This seems weird to create a dialog but not
show it. Seems the functionality shouldn't be in the dialog, but some
helper class that can be called without creating a whole dialog with all
it's unnecessary overhead of window initialization, etc. So maybe the EQ
experts can consider factoring that out. And why is DontPromptUser
called only on the 2nd Preview? Haven't looked into these aspects, just
fixed it.

Anyway, I patched it by saving and restoring the real dialog to the
Effect, around the creation of the temp, so it's fixed for now. Any
other "fake" dialogs in effects?

Committed the code, per Richard's vote and your all's testing. Will
build an rc5 and notify this list when it's posted.

- V


Gale Andrews wrote:

> | From Vaughan Johnson <vaughan@...>
> | Mon, 05 May 2008 00:26:09 -0700
> | Subject: [Audacity-devel] 1.3.5 rc1 effect dialogs go modeless
>  
>> I implemented the fix a little more OOP-ish:...
>>         Added the arg to both ProgressHide calls in Effect::Preview(). I
>>         think that handles the 'not ideal', because Mix-and-Render
>>         doesn't have a controls dialog, so it's okay to re-enable the
>>         Project window, right?
>>
>> This involved 2-3 lines of changes in about 20 files. So the question is
>> whether to put all those changes into 1.3.5.
>>
>> I posted a 1.3.5-rc4 Windows installer with these changes, built on
>> latest CVS (incl. locale updates), at
>> http://audacity.sourceforge.net/files/audacity-win-unicode-1.3.5-rc4.exe 
>> , but NOT committed these progress-vs-modality changes to CVS.
>>
>> If there's time to test them on Windows, should we put them into 1.3.5?
>> If not, we can just build the release from CVS. If so, even if more
>> problems show up, we can probably fix by 1.3.6.
>>    
>
> I've tested RC4 with a number of effect dialogues and the dialogue remains
> modeless after preview now. I also tried doing something in the main  
> window when previewing, and when mixing and rendering and preparing
> preview for a longer preview, and could not.
>
> However there is a replicable problem now in Equalization (but not the
> other effects I tried). If I preview the EQ effect, even a short preview
> with only a "Previewing" dialogue, cancel it, then preview and cancel
> the preview a second time, there is a crash. Tested with three different
> files so the file is not the problem.
>
> This scenario does not crash a recent CVS build without the current
> modeless fix. So it does not look like this should be committed into
> 1.3.5, at least without a warning.      
>
>
>
> Gale
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Audacity-devel mailing list
> Audacity-devel@...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>
>  

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Vaughan Johnson
1.3.5-rc5 for Windows posted
Reply Threaded More
Print post
Permalink
http://audacity.sourceforge.net/files/audacity-win-unicode-1.3.5-rc5.exe

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Richard Ash (audacity-help)
Re: 1.3.5-rc5 for Linux posted
Reply Threaded More
Print post
Permalink
http://audacity.sourceforge.net/files/audacity-src-1.3.5-rc5.tar.bz2

Richard


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel