Mercurial > pidgin
view libpurple/purple-client-example.c @ 30287:c2b3bfb2fe35
When setting an Avatar image via the Gallery bot, the MXit server pushes
a Get Extended Profile response to inform the client. The MXitId field in that
packet happens to be set to the user's MXitid and not empty so the libpurple
plugin assumes it was a request for a buddies profile information so a profile
popup is displayed.
We now check if the MXitId field is empty or if it matches the user's MxitId
(returned in the Login reponse).
author | andrew.victor@mxit.com |
---|---|
date | Mon, 19 Jul 2010 08:56:03 +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; }