Version: 0.7.2 (using KDE 3.4.0, Debian Package 4:3.4.0-0pre2 (3.1)) Compiler: gcc version 3.3.5 (Debian 1:3.3.5-8) OS: Linux (i686) release 2.6.10-1-686 In my usage pattern I never ever wanted to run two digikam instances for the _same_ image library path. It would be therefore nice if clicking/starting digikam again it would just jump to already running instance with the same (default) image library path. Achim
Gilles, should we close this wish? I guess digiKam is supposed to open more than once, right? We will not change this behavior? Andi
Andi, To do what Achim want, some code need to be add to check if digiKam already run in current desktop session. We need to take a look in other application how is done, like Kmail. I think this code must be add to main.cpp or in digikamapp.cpp. Gilles
Oh I just re-read this bugreport, I guess I misunderstood it in the first place. I thought that he meant that digiKam should never ever be started twice, but this is what we want to be able to, right? But he is talking about the library path... I see now. This is another situation. Andi
@gilles: Kmail is a unique app. So kdecore makes sure no second instance is started. Two use cases: 1) click the digikam icon in kicker or plasma-panel. Action: digikam is started if not already running _or_ jumps to the workspace with a running digikam and brings it to the front of all windows. 2) camera in plugined and digikam selected as tool of choice: Action: digikam is started and download dialog is opened _or_ jumps to the workspace with a running digikam and brings it to the front of all windows and opens the download dialog. Usecase 2 is currently partially implemented with the helper script hotplug/digikam-camera. But if digikam is running in a different workspace one never sees that the download dialog was opened :( Achim P.S: @Andi: never had a usecase to run 2 digikam apps, so unique app would be fine with me ;)
Marcel, What's the sattus of this entry with 2.0.0 ? Gilles Caulier
I think there are use cases to run more than one instance, even if it is not common. It works fine anyway, no need to restrict user. I suggest to close.
Ok fine for me. Gilles