Mercurial > pidgin
view libpurple/purple-send-async @ 25409:0f2503390a6b
Change our ICQ client ID such that we identify ourselves to the ICQ servers as
ICQ Basic 14.34.3096. This is the same client ID a number of other third-party
clients are using with no issues. I have also added a new definition for this
ICQ Basic version and changed the CLIENTINFO_ICQ_KNOWNGOOD defiinition to
reflect this. Effects of this change are that available messages and buddy
icons are now published correctly and visible to other clients. Fixes #6235.
Thanks to Dimmuxx and h3llfire for pointing this out.
author | John Bailey <rekkanoryo@rekkanoryo.org> |
---|---|
date | Mon, 02 Feb 2009 22:20:04 +0000 |
parents | 942bf314fc8a |
children | 584063555949 |
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. 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