Bug 103371

Summary: Only one digikam instance should run on the same image library path
Product: [Applications] digikam Reporter: Achim Bohnet <ach>
Component: Setup-CLIAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: wishlist CC: caulier.gilles
Priority: NOR    
Version: 0.7.2   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In: 1.9.0
Sentry Crash Report:

Description Achim Bohnet 2005-04-06 19:37:14 UTC 
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
Comment 1 Andi Clemens 2008-08-18 09:27:00 UTC 
Gilles,

should we close this wish? I guess digiKam is supposed to open more than once, right? We will not change this behavior?

Andi
Comment 2 caulier.gilles 2008-08-18 09:45:07 UTC 
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
Comment 3 Andi Clemens 2008-08-18 09:51:54 UTC 
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
Comment 4 Achim Bohnet 2008-09-17 17:57:10 UTC 
@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 ;)
Comment 5 caulier.gilles 2011-02-03 09:24:04 UTC 
Marcel, 

What's the sattus of this entry with 2.0.0 ?

Gilles Caulier
Comment 6 Marcel Wiesweg 2011-02-03 21:59:39 UTC 
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.
Comment 7 caulier.gilles 2011-02-03 22:28:27 UTC 
Ok fine for me.

Gilles