BUGREPORT 1.1final - 2 instances of KDevelop

[Hummel, Timo]

I think the reason is another here. KDevelop creates a file somewhere, and
if KDevelop crashes, the file remains so that KDevelop notices that it
wasn't shut down correctly last time. If you run another instance, it
notices that the file is still there and assumes that KDevelop crashed, but
it is still running. Another idea would be to use interprocess
communications or simple a ps and if kdevelop sees itself plus one instance,
and the file is existant, everything is alright. If there is only one
instance, it indicates that kdevelop really crashed.


-----Original Message-----
From: Falk Brettschneider [mailto:gigafalk at yahoo.com]
Sent: Montag, 28. Februar 2000 15:04
To: kdevelop
Subject: BUGREPORT 1.1final - 2 instances of KDevelop


Hi,

Whenever I start a second instance of KDevelop, a message appears that
KDevelop wasn't closed correctly the session before. But that's not
true. And I don't think that it is necessary that KDevelop asks "Do you
want to start with the last loaded profile?" in that case.
-- 

Ciao,
--Falk

__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com