Hi,
On Thursday 14 May 2009 17:14:35 you wrote:
> Yeah, this is on my TODO list; the API is still unstable so it's not a
> problem to change this.
[...]
> That said, the right solution is, of
> course, to fix the services but since D-Bus is so free-form and we don't
> have validation tools (yet) y
On Thu, 2009-05-14 at 14:35 +0200, Davide Bettio wrote:
> Hi,
>
> It seems that according to dbus specs dashes aren't allowed, so all the
> properties have wrong names (like daemon-version).
Yeah, this is on my TODO list; the API is still unstable so it's not a
problem to change this.
> Accordi
Hi,
On Thursday 14 May 2009 14:53:23 Kay Sievers wrote:
> Did you check DeviceKit-disks and DeviceKit-power for the naming
> issues you mention here?
Sorry, I've forgot to mention that I'm experiencing naming issues with
DeviceKit-disks.
Bye,
Davide Bettio.
_
On Thu, May 14, 2009 at 14:35, Davide Bettio wrote:
> It seems that according to dbus specs dashes aren't allowed, so all the
> properties have wrong names (like daemon-version).
> According to the specs, «Interface, signal, method, and property names are
> "WindowsStyleCaps", note that the first
Hi,
It seems that according to dbus specs dashes aren't allowed, so all the
properties have wrong names (like daemon-version).
According to the specs, «Interface, signal, method, and property names are
"WindowsStyleCaps", note that the first letter is capitalized, unlike Java».
I suggest you to
