> There's no rule of what the client service names should be.
Well if you're going by the spec[1] then clients should have names in a specific
format:
> Each application can register an arbitrary number of Status Notifier Items by
> registering on the session bus the service
> org.freedesktop.Sta
There's no rule of what the client service names should be.
The only service name that matters is the watcher.
The others register to the watcher so we can get their service name then.
David
On 9 May 2017 00:41, "Calvin Lee" wrote:
> It seems that other applications use the "Unique DBus name"
> It seems that other applications use the "Unique DBus name" (example ":1.12")
> only or service names which don't obey the naming rule.
Nice catch! I think that this is the fault of the "xembed-sni-proxy" that
translates xembed programs to the SNI protocol. Native StatusNotifier programs
like Ko
Simple answer. We shouldn't.
I'll try and fix it.
On Saturday 06 May 2017 20:46:03 Calvin Lee wrote:
> Hello,
>
> Recently I have been implementing The StatusNotifierItem[1] protocol for
> the sway window manager. I have been using KDE programs to test my
> implementation because KDE has stated that it uses the protocol. However,
> it seems that i
Hello,
Recently I have been implementing The StatusNotifierItem[1] protocol for the
sway window manager. I have been using KDE programs to test my implementation
because KDE has stated that it uses the protocol. However, it seems that instead
of using the 'org.freedesktop.*" namespace that is defi
