Fix for non-responsive timeline and meters after a timer record
The problem is that the fix for bug #334 is a bit over zealous and blocks ALL application level events instead of just the keyboard events. This was blocking the new AUDIOIO event from being handled. I didn't want to monkey with the #334 solution at this time, so the simple fix was to ensure the progress dialog was going (thus, enabling appilcation events) was destroyed before attempting to stop the audio stream.
This commit is contained in:
parent
b09c923e92
commit
70285448c9
|
@ -270,8 +270,12 @@ bool TimerRecordDialog::RunWaitDialog()
|
|||
updateResult = progress.Update();
|
||||
bIsRecording = (wxDateTime::UNow() <= m_DateTime_End); // Call UNow() again for extra accuracy...
|
||||
}
|
||||
pProject->OnStop();
|
||||
}
|
||||
|
||||
// Must do this AFTER the timer project dialog has been deleted to ensure the application
|
||||
// responds to the AUDIOIO events...see not about bug #334 in the ProgressDialog constructor.
|
||||
pProject->OnStop();
|
||||
|
||||
// Let the caller handle cancellation or failure from recording progress.
|
||||
if (updateResult == eProgressCancelled || updateResult == eProgressFailed)
|
||||
return false;
|
||||
|
|
Loading…
Reference in New Issue