Mercurial > pidgin
view libpurple/purple-client-example.c @ 22756:17cda378a2dd
Added "chat-join-failed" signal, emitted by a new serv_got_join_chat_failed()
function in server.c. This is emitted with the PurpleConnection and
chat name and allows a UI or plugin which was expecting a group chat to be
joined to know if failure occurred.
serv_got_join_chat_failed() is only called by jabber so far; I know that
at least oscar should call it some situations, as well, such as when a
busted SNAC error is received after trying to join a chat with an invalid
room name.
author | Evan Schoenberg <evan.s@dreskin.net> |
---|---|
date | Tue, 29 Apr 2008 01:46:40 +0000 |
parents | 48d09d62912e |
children |
line wrap: on
line source
#ifndef DBUS_API_SUBJECT_TO_CHANGE #define DBUS_API_SUBJECT_TO_CHANGE #endif #include <stdio.h> #include <stdlib.h> #include "purple-client.h" /* This example demonstrates how to use libpurple-client to communicate with purple. The names and signatures of functions provided by libpurple-client are the same as those in purple. However, all structures (such as PurpleAccount) are opaque, that is, you can only use pointer to them. In fact, these pointers DO NOT actually point to anything, they are just integer identifiers of assigned to these structures by purple. So NEVER try to dereference these pointers. Integer ids as disguised as pointers to provide type checking and prevent mistakes such as passing an id of PurpleAccount when an id of PurpleBuddy is expected. According to glib manual, this technique is portable. */ int main (int argc, char **argv) { GList *alist, *node; purple_init(); alist = purple_accounts_get_all(); for (node = alist; node != NULL; node = node->next) { PurpleAccount *account = (PurpleAccount*) node->data; char *name = purple_account_get_username(account); g_print("Name: %s\n", name); g_free(name); } g_list_free(alist); return 0; }