This will listen for a signal on the system DBus to show a notification to all users on the current machine. This allows prettier and more versatile notifications than using wall/write.
This is disabled by default but can be enabled in e.g. ~/.config/plasmashellrc per user or /etc/xdg/plasmashellrc globally
[Notifications] ListenForBroadcasts=true
Requested by LiMux project
Little test app that works.
If "uids" is given, the notification will only be shown for the users with UIDs given. If it is omitted the notification is shown for all users.
#include <QCoreApplication>
#include <QDBusConnection>
#include <QDBusMessage>
#include <QTimer>
int main(int argc, char *argv[])
{
QCoreApplication app(argc, argv);
QDBusMessage message = QDBusMessage::createSignal(QStringLiteral("/de/limux/Broadcast"),
QStringLiteral("org.kde.BroadcastNotifications"),
QStringLiteral("Notify"));
message.setArguments({ QVariantMap{
{QStringLiteral("summary"), "Cannot restore network shares"},
{QStringLiteral("body"), "Please contact system administration if you cannot find your stuff."},
{QStringLiteral("appIcon"), QStringLiteral("network-disconnect")},
{QStringLiteral("uids"), QStringList{QStringLiteral("0"), QStringLiteral("1000"), QStringLiteral("1337")} }
} });
QDBusConnection::systemBus().send(message);
QTimer::singleShot(500, &app, QCoreApplication::quit);
return app.exec();
}
| Automatic diff as part of commit; lint not applicable. |
| Automatic diff as part of commit; unit tests not applicable. |
Note that actions won't work, we'd always be replying on the session bus. (this is solvable)
| dataengines/notifications/notificationsengine.cpp | ||
|---|---|---|
| 70 | I'd get rid of the plasmashell in the iface name. Also for whatever reason convention is to be UpperCamelCase (i.e BroadcastNotification not broadcastNotification) | |
| 426 | is it intended that you can't send a message to root? otherwise toULongLong(&rc ); | |
What would be the best place to put a little utility (similar to notify-send or kdialog --passivepopup) for this?
No, you're right. I mistakenly thought actions were in the hints even though the code even has "{} //no actions" documented