Replies: 1 comment 4 replies
-
The "D-Bus Proxy" construct captures a unique service and object path, so it would not be appropriate to create one without an object path. However, it definitely would be nice to be able to register a signal handler with an arbitrary match rule from an |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am trying to catch Bluetooth Low Energy connections and disconnections from known (meaning, the system has seen them) devices in BlueZ. Normally, this requires looking for a PropertiesChanged signal emitted with the Connected property set to either True or False. This would be relatively simple, except that I would need to keep track of the MAC address of all known devices, because these signals are emitted from paths that look like /org/bluez/hci0/dev_{MAC address of device}. I could keep a list of all devices on the tree, but I would prefer to be lazy and instead get a hander for all such signals, no matter who is emitting them. In python-dbus, it is possible to set up a handler for the whole bus without specifying a path. Is such a thing possible in sdbus-c++? It seems to me that sdbus::Proxy classes require objectPath in every constructor. Thanks in advance for any guidance you can offer!
Beta Was this translation helpful? Give feedback.
All reactions