Bugzilla – Bug 903
Windows: No longer possible to create a new, empty project window by executing the app again
Last modified: 2018-08-20 11:45:15 UTC
Was that supposed to "work" in 2.0, or was that a bug? It's very easy to crash Audacity 2.0.5 if you open two instances like that.
(In reply to comment #1) Steve wrote: > It's very easy to crash Audacity 2.0.5 if you open two instances like that. On what OS? An XP virtual machine? Although (for apps that support multiple instances) executing the same app on Windows would open a second instance of that app, in Audacity that only used to open a new project window in the same instance of Audacity. I've tried executing 2.0.5 again while recording and while applying an effect on Win 7 and Win 8, and a new project window opens without a crash. We already allow in 2.1.0 using Open with to import a file into a new project window while recording or while applying real-time preview. If you try to Open with while exporting or while applying an effect, the import is queued and takes place after export or the effect is completed.
I think this falls under the whole multiple instance, multiple project conundrum. Solving that will be a whole project in itself and we're going to have to "forget" past behavior and precisely define how it should all be handled. I fear it will not be a quickie problem to solve either. :-(
(In reply to comment #1) Actually it appears that I've found a new bug, and it is not specific to the case in question (though initially it looked like it was). I'll investigate further and then post a new bug report if necessary.
(In reply to comment #3) Leland wrote: > "forget" past behavior and precisely define how it should all be handled. I fully understand we're trying to solve multiple issues on three platforms. Nonetheless I think for Windows the definite expectation is that executing the same audacity.exe again would open a new Audacity project window. That did used to work, and users can see that "Open with" is already allowed to open new project windows. But yes we have to consider what multiple project actions are safe to allow at the same time.
(In reply to comment #5) > (In reply to comment #3) > Leland wrote: > > "forget" past behavior and precisely define how it should all be handled. > I fully understand we're trying to solve multiple issues on three platforms. > > Nonetheless I think for Windows the definite expectation is that executing the > same audacity.exe again would open a new Audacity project window. That did used > to work, and users can see that "Open with" is already allowed to open new > project windows. > And that's just fine. We just need to make sure that is one of the criteria/rules when we straighten out the multi-mess. :-)
closed as NOTABUG - this is intended, desired behavior
