Mercurial > pidgin
view libpurple/purple-send-async @ 20878:38b12aff6d5a
deryni noticed that my previous fix didn't address what was really wrong with this function. The request callback was removing stuff from the request internals without cleaning up. This is also cleaner and (hopefully) less error prone. I'm not at all happy with how other parts of this work, but I don't have a good way of testing, so I'm not going to make drastic changes.
author | Daniel Atallah <daniel.atallah@gmail.com> |
---|---|
date | Wed, 10 Oct 2007 20:29:16 +0000 |
parents | 598b1b15b199 |
children | 942bf314fc8a |
line wrap: on
line source
#!/bin/bash METHOD_NAME=$1 if test -z "$METHOD_NAME" then cat <<EOF This program calls purple API functions using DBus. As opposed to purple-send, it does not print the return value. Usage: $0 method-name type1:parameter1 type2:parameter2 ... This shell script just invokes dbus-send, see man dbus-send for how to specify the parameters. Examples: $0 PurpleCoreQuit Use dbus-viewer to get the list of supported functions and their parameters. EOF exit 1 fi shift dbus-send --dest=im.pidgin.purple.PurpleService --type=method_call /im/pidgin/purple/PurpleObject im.pidgin.purple.PurpleInterface.$METHOD_NAME "$@" echo