diff options
| author | Patrick Ohly <patrick.ohly@intel.com> | 2012-05-11 19:09:01 +0000 |
|---|---|---|
| committer | Patrick Ohly <patrick.ohly@intel.com> | 2012-05-11 19:09:01 +0000 |
| commit | 5577786ba2ae314430a2b2d0f81bfdb976751d05 (patch) | |
| tree | 54cd5c68e2a1b401b085fe52348e8d6eeca4e6a4 /src/gdbusxx/gdbus-cxx-bridge.h | |
| parent | 5735f30aeb1ff11f99029b11bcc1aa44591cb206 (diff) | |
GDBus GIO: disable usage of "closed" signal
Testing showed that using the "closed" signal leads to unexpected
error messages, perhaps because it also gets delivered for normal
shutdown. Better use the traditional, known-to-work "monitor method
call" method.
Diffstat (limited to 'src/gdbusxx/gdbus-cxx-bridge.h')
| -rw-r--r-- | src/gdbusxx/gdbus-cxx-bridge.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/gdbusxx/gdbus-cxx-bridge.h b/src/gdbusxx/gdbus-cxx-bridge.h index c6de6ee6..289c3ae4 100644 --- a/src/gdbusxx/gdbus-cxx-bridge.h +++ b/src/gdbusxx/gdbus-cxx-bridge.h @@ -140,7 +140,7 @@ class DBusConnectionPtr : public boost::intrusive_ptr<GDBusConnection> typedef boost::function<void ()> Disconnect_t; void setDisconnect(const Disconnect_t &func); -#define GDBUS_CXX_HAVE_DISCONNECT 1 + // #define GDBUS_CXX_HAVE_DISCONNECT 1 }; class DBusMessagePtr : public boost::intrusive_ptr<GDBusMessage> |