view doc/dbus-server-signals.dox @ 22136:9df0a8c7c9b7

* Clarify the documentation for purple_request_action's 'default_ation' It should be the action that users are most likely to choose * Fix Pidgin's request_action dialog to correctly set the default action based on the input value. We were counting from the button on the left and moving right but we should have started counting from the button on the right and moved left, because that's the order the actions are specified in when passed to purple_request_action.

/** @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