Mercurial > pidgin
view libpurple/purple-client-example.c @ 16278:70a368273778
Fix that pesky ICQ "Unable to add buddy 1" error. Basically we were
trying to add something to our server-stored buddy list, but there
was no "master container" to add the item to. For normal buddies the
oscar code added the master container if needed, but that wasn't
happening for things like the buddy icon item, or the permit/deny item.
So if you had an empty buddylist and you attempted to set an icon
for your icq account, or you changed your privacy setting, or you
went invisible or not invisible then you'd see the error.
author | Mark Doliner <mark@kingant.net> |
---|---|
date | Fri, 20 Apr 2007 06:51:33 +0000 |
parents | c6e563dfaa7a |
children | 48d09d62912e |
line wrap: on
line source
#define DBUS_API_SUBJECT_TO_CHANGE #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; }