Mercurial > pidgin
view libpurple/purple-send @ 24532:d70eb6304eae
Use separate variables to keep track of the timer and the watcher.
I believe only one of these will be used at any given time, and so
while there is no overlap in their usage we need to use different
variables so that we can call either purple_input_remove or
purple_timeout_remove depending on the usage. I don't think this
matters with glib because purple_input_remove and
purple_timeout_remove both call g_source_remove, but it could be
an issue when using other event loops.
There's also the problem in line 673 where we add the watcher, but
then if the call to msn_soap_write_cb fails we add a timer using
the same variable. That's still going to be a little buggy.
author | Mark Doliner <mark@kingant.net> |
---|---|
date | Tue, 25 Nov 2008 02:43:56 +0000 |
parents | 942bf314fc8a |
children | cea56d000b16 |
line wrap: on
line source
#!/bin/sh METHOD_NAME=$1 if test -z "$METHOD_NAME" then cat <<EOF This program calls purple API functions using DBus and prints the return value. If you are not interested in the return value, use purple-send-async. 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 PurpleAccountsFindConnected string: string:prpl-jabber $0 PurpleAccountsGetAll $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 --print-reply --type=method_call /im/pidgin/purple/PurpleObject im.pidgin.purple.PurpleInterface.$METHOD_NAME "$@" echo