D9094: Use a faster way to determine kio-stash isn't installed

[arnav dhamija]

shortstheory added a comment.


  Sorry for the late reply, I have endsem college exams atm.
  
  How do daemons register themselves on Windows' KDED5 module (if there is one)? Otherwise, the patch looks good.
  
     QDBusMessage msg;
     QDBusMessage replyMessage;
     msg = QDBusMessage::createMethodCall(
               "org.kde.kio.StashNotifier", "/StashNotifier", "", "pingDaemon");
     replyMessage = QDBusConnection::sessionBus().call(msg);
     if (replyMessage.type() == QDBusMessage::ErrorMessage) {
         qDebug() << "Launching fallback daemon";
         const QString program = "./testdaemon";
         stashDaemonProcess->start(program);
    }
  
  I've been doing it like this for testing if the stash daemon is active for the unit tests. This makes sure that the caller is able to use DBus and get replies from it successfully. Perhaps that should change to the approach used in this patch as well...

REPOSITORY
  R318 Dolphin

REVISION DETAIL
  https://phabricator.kde.org/D9094

To: hein, davidedmundson, elvisangelaccio, shortstheory
Cc: alexeymin, ngraham, #dolphin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.kde.org/mailman/private/kfm-devel/attachments/20171204/1355f822/attachment.htm>