On Wed, 2011-02-16 at 22:47 +0100, Marco Martin wrote: > On Wednesday 16 February 2011, you wrote: > > > > Oh, I thought you meant to use "AccessibleDescription" as a suffix. > > > > I guess my concern with not having two is that it means when there is a > > state change signal we've got to do a DBus round trip before we can > > accurately display that state change. With having two we can grab the > > description when we get the icon changed signal (or attention icon > > changed) when, in theory, the description would change as well. > > > > Another approach would be to add a signal for when the description > > changed. > > > > What do you think? > > well, probably thinking with our implementation too much in mind.. > in the end we found that asking for single properties in dbus had so round > trip that we just get everything when anything changes, transeffing even a > big > a mount of data is fast, the asking and waiting for the dbus response is > less, > so even when just changes the state, (or any other property for twhat > matters) > we just re get everything (that is not pretty but is actually faster than > just > getting 3-4 properties one after the other). > > now yeah this could not be adapt to a defferent implementation.
I guess I understand getting all if you're needing to get any
properties, but certainly you don't do that on a status update, right?
It would seem that you don't need any properties to change the status.
--Ted
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
