Mercurial > pidgin
view src/gaim-client-example.c @ 13832:d1fdde7cfc0a
[gaim-migrate @ 16281]
SF Patch #1500640 from bsponline
Fixes SF Bug #1493888
The bug description is:
"These are the steps you need to take to reproduce the
bug in beta3:
1. expand a contact.
2. re-arrange the protocol order for the contact.
3. do NOT collapse the contact.
4. hover over another contact.
The other contact will auto-expand too, which it should
not."
committer: Tailor Script <tailor@pidgin.im>
| author | Richard Laager <rlaager@wiktel.com> |
|---|---|
| date | Mon, 19 Jun 2006 05:17:54 +0000 |
| parents | c9312177821a |
| children | 8bda65b88e49 |
line wrap: on
line source
#define DBUS_API_SUBJECT_TO_CHANGE #include <stdio.h> #include <stdlib.h> #include "gaim-client.h" /* This example demonstrates how to use libgaim-client to communicate with gaim. The names and signatures of functions provided by libgaim-client are the same as those in gaim. However, all structures (such as GaimAccount) 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 gaim. 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 GaimAccount when an id of GaimBuddy is expected. According to glib manual, this technique is portable. */ int main (int argc, char **argv) { GList *alist, *node; gaim_init(); alist = gaim_accounts_get_all(); for (node = alist; node; node = node->next) { GaimAccount *account = (GaimAccount*) node->data; char *name = gaim_account_get_username(account); g_print("Name: %s\n", name); g_free(name); } g_list_free(alist); return 0; }
