Mercurial > pidgin
view libpurple/purple-send-async @ 18618:2f0bda21712f
purple_request_action doesn't call any callbacks if the user closes the
window instead of clicking on the buttons. The problem is that
purple_request_action is not required to have a cancel action, so when the
close button is clicked the UI has no idea which action should be called.
The closest one would be the default action, but when the user clicks
cancel, he probably expects to cancel even if that's not the default action.
Workaround by telling the window manager we don't want to have a close
button. Fixes #1947
author | Ka-Hing Cheung <khc@hxbc.us> |
---|---|
date | Mon, 23 Jul 2007 02:33:41 +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