dfaure added a comment.
Yes interface->isServiceRegistered(dbusServiceName) is technically blocking, but it can't block for a long time, since it's only talking to the dbus daemon. The reply comes in rather quickly, unlike a blocking call to another KDE process which could be busy or where the call itself could take a long time to be processed. In summary, I don't think an existing call to isServiceRegistered can be used as an argument for making (potentially much much longer) blocking calls. REPOSITORY R289 KNotifications REVISION DETAIL https://phabricator.kde.org/D4799 EMAIL PREFERENCES https://phabricator.kde.org/settings/panel/emailpreferences/ To: vpilo Cc: dfaure, broulik, graesslin, mck182, #frameworks
