doesn't notice signal without method call about sdbus-cpp HOT 7 CLOSED

The problem is that no event loop was run in your example for the connection. One must call enterEventLoop() or enterEventLoopAsync() method of the connection object. Perhaps that is not specified clearly in the sdbus-c++ tutorial...

from sdbus-cpp.

Or you can simply create sessionResponse like this: auto sessionResponse = sdbus::createProxy(sdbus::createSessionBusConnection(), destinationName, sessionResponsePath);, which, according to https://github.com/Kistler-Group/sdbus-cpp/blob/master/docs/using-sdbus-c%2B%2B.md#using-d-bus-connections-on-the-client-side means that the proxy will get an owner of the connection and will automatically run the event loop on it for your convenience (hence signals would work fine for you), and create createSession like this: auto createSession = sdbus::createProxy(sdbus::createSessionBusConnection(), destinationName, objectPath, sdbus::dont_run_event_loop_thread);, which has the proxy create another connection, but whose event loop would not be run because you just use it to call a method and then let go of it, as described again in https://github.com/Kistler-Group/sdbus-cpp/blob/master/docs/using-sdbus-c%2B%2B.md#using-d-bus-connections-on-the-server-side, so this saves time and resources.

from sdbus-cpp.

That was quick, thanks. I only looked at the client side of the tutorials. Now I see and it works.

from sdbus-cpp.

Out of curiosity, how does this example look in rust with the zbus library? Can you paste the code? I wonder if I can simplify anything here :-)

from sdbus-cpp.

Very similar but with more macro magic. main.txt

The official example is probably more helpful than my code: https://dbus2.github.io/zbus/client.html

from sdbus-cpp.

I like that zbus can deserialize 'a{sv}' into structs instead of maps. https://dbus2.github.io/zbus/faq.html
I think this feature fits cpp just as well.

from sdbus-cpp.

@FuchtelJockel I think that would be possible in sdbus-c++, too. The user would, however, need to additionally describe his struct (through some sort of sdbus-c++-provided macros, for example) so that sdbus-c++ would know understand the struct's members, their names, position etc.

I may add this to my TODO list.

from sdbus-cpp.