view doc/dbus-server-signals.dox @ 12145:5bda6a03d43b

[gaim-migrate @ 14446] A fix for SimGuy. He says that we should actually honor the system log preference under all cases. I suppose, maybe he's right. (01:05:24) Kevin Stange (SimGuy): I have the system log off (01:05:33) Kevin Stange (SimGuy): and yet somehow my own status changes are winding up in it (01:05:56) Kevin Stange (SimGuy): seems to just be idle changes (01:06:16) Kevin Stange (SimGuy): ---- +++ kevin_m_stange became unidle @ 2005-11-16 09:04:06 ---- (01:06:33) Kevin Stange (SimGuy): it is only logging my own idleness changes :) (01:07:10) Kevin Stange (SimGuy): I was just messing around and opening the dialogs from the tools menu and rather than being warned I have no system log, it showed me my system log, which shouldn't have happened :) (01:11:35) Kevin Stange (SimGuy): rlaager: it's clearly because of line ~ 1353 in status.c not checking the preference committer: Tailor Script <[e-mail]>

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

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

 <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 tw=75 et