From 8e17757ae3cbdd93b200258eb646ee5408e9fdea Mon Sep 17 00:00:00 2001 From: Frank Reininghaus Date: Thu, 20 Aug 2009 15:47:38 +0000 Subject: Use KApplication::sessionSaving() to determine if Dolphin is closed by the session manager - there's no need to reinvent the wheel ;-) Thanks to Lubos Lunak for the hint. svn path=/trunk/KDE/kdebase/apps/; revision=1013726 --- src/dolphinapplication.cpp | 13 +------------ 1 file changed, 1 insertion(+), 12 deletions(-) (limited to 'src/dolphinapplication.cpp') diff --git a/src/dolphinapplication.cpp b/src/dolphinapplication.cpp index 988019de1..f61bf795a 100644 --- a/src/dolphinapplication.cpp +++ b/src/dolphinapplication.cpp @@ -28,7 +28,7 @@ #include DolphinApplication::DolphinApplication() : - m_lastId(0), m_closedBySessionManager(false) + m_lastId(0) { new ApplicationAdaptor(this); QDBusConnection::sessionBus().registerObject("/dolphin/Application", this); @@ -100,17 +100,6 @@ int DolphinApplication::newInstance() return 0; } -bool DolphinApplication::closedBySessionManager() const -{ - return m_closedBySessionManager; -} - -void DolphinApplication::commitData(QSessionManager& sessionManager) { - m_closedBySessionManager = true; - KUniqueApplication::commitData(sessionManager); - m_closedBySessionManager = false; -} - int DolphinApplication::openWindow(const KUrl& url) { DolphinMainWindow* win = createMainWindow(); -- cgit v1.3