view doc/dbus-server-signals.dox @ 24134:aa8ddc4e12af

GtkBlist: don't set the Urgent hint whenever a connection error occurs or is updated In principle, setting Urgent is a good idea, because the user can tell that an error has occurred. However, it winds up being repeatedly re-set every time an account tries and fails to reconnect, which is incredibly annoying. I think the right solution is to keep a set of accounts we've set urgent for, removing them from the set when they successfully connect. But not setting it at all is better than the current state.

/** @page dbus-server-signals DBus Server Signals

 @signals
  @signal dbus-method-called
  @signal dbus-introspect
 @endsignals

 @see dbus-server.h

 <hr>

 @signaldef dbus-method-called
  @signalproto
gboolean (*dbus_method_called)(DBusConnection *connection,
                               DBusMessage *message);
  @endsignalproto
  @signaldesc
   Emitted when a dbus method is going to be called.
  @param connection The DBus connection.
  @param message The DBus message.
  @return TRUE if signal handler handled the method. ???
 @endsignaldef

 @signaldef dbus-introspect
  @signalproto
void (*dbus_introspect)(GList **bidings_list);
  @endsignalproto
  @signaldesc
   ???
  @param bindings_list ???
 @endsignaldef

 */
// vim: syntax=c.doxygen tw=75 et