Andrey Sidorov
Andrey Sidorov
As these are all signal the easiest way is just to listen all messages and check if message is from service ```js var dbus = require('dbus-native'); var conn = dbus.createConnection();...
I'll try to test this code in couple of hours when I beck home at my desktop computer
so my example is definitely not enough. In order to receive signals client must send AddMatch message first try this to see listen for all events: ```js var dbus =...
Message is plain object, to better understand semantics of what's there best start is dbus spec: https://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-messages Also if you want to continue with "low level" approach (not via automatic...
I was thinking about it, but might be a bit too early? Maybe OK to go with migger api changes ( async/await etc ) in major version.
what's value of `DBUS_SESSION_BUS_ADDRESS` env variable?
could you add console.log here https://github.com/sidorares/dbus-native/blob/35318c23bde92cc2cd877ade89a9bbf1a958217f/index.js#L45 and see what's actually passed to `abs.connect()` ?
We really want to allow `{a: "foo", b: "bar", c: 42}` to be used for "a{sv}" but at the moment it's quite verbose, you have to go through each step...
I can't see existing helper in object itself ( feel free to add it ), but on low level signals are just messages with type=signal. Use `bus.sendSignal` for that -...
at the moment it's only implemented on a service side - if your interface implementation object has "emit" function, calling it result in emitting dbus signal (in addition to node...