Re: bug 96 (Re: [Audacity-devel] 1.2.0?)
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Dominic M. <do...@mi...> - 2003-12-18 07:19:55
|
On Dec 16, 2003, at 3:21 PM, Vaughan Johnson wrote: >>> All platforms use that wxSingleInstanceChecker code, but do they >>> follow the same sort of startup procedure, i.e., always try to >>> create a new process? Sorry, I don't know Linux or Mac well enough. >>> >> >> On Linux there are programs (like Mozilla) that have their own shell >> script which checks if a process is already running. >> > > Does Audacity? Would that be preferrable to concept #2? I don't think it's much of an issue on Linux and Mac OS X. On Mac OS (both 9 and X, actually), double-clicking a document ALWAYS sends the open message to an already-running process, if an appropriate one exists. Audacity has a flag set so that Mac OS won't let the user open two processes anyway, even if they wanted. The only way a user could get two Audacity processes running would be to duplicate the executable and run both of them at once (or run two versions). Then they'll see the dialog that another version is running. On Linux, AFAIK there's no way to open a "document", i.e. double-click on a document and have it open the appropriate application. Then again, maybe KDE and GNOME have ways to do this, but I have no idea how it works. Even if they do, I doubt many people use them. Point being, whatever's the best solution on Windows is what we should do. Don't worry about the other platforms for this particular issue; we can consider addressing Linux and KDE/GNOME later if anyone complains. - Dominic |