libpurple, the nullclient and AIM

[Jeremy Trammell - Setaris]

I've done a variety of things towards that end, but to keep things
simple I am now focusing on simply using the example nullclient code, as
provided, which does pass a set of glib io handlers in the
PurpleEventLoopUiOps structure.

static PurpleEventLoopUiOps glib_eventloops =
{
    g_timeout_add,
    g_source_remove,
    glib_input_add,
    g_source_remove,
    NULL,
#if GLIB_CHECK_VERSION(2,14,0)
    g_timeout_add_seconds,
#else
    NULL,
#endif

    /* padding */
    NULL,
    NULL,
    NULL
};


Jeremy Trammell
Chief Technology Officer
	  	509 East 87th St. #1W
New York, NY 10128
Setaris Corporation 	cell +1.518.331.5180
www.setaris.com <http://www.setaris.com> 	fax +1.646.786.4370
 

INTELLIGENT SOFTWARE


------------------------------------------------------------------------


------------------------------------------------------------------------
*From:* Daniel Atallah <datallah at pidgin.im>
*To:* Jeremy Trammell - Setaris <jeremy.trammell at setaris.com>
*CC:* support at pidgin.im
*Sent:* 07/06/2009 4:11:49 PM -0400
*Subject:* libpurple, the nullclient and AIM


> On Mon, Jul 6, 2009 at 4:07 PM, Jeremy Trammell -
> Setaris<jeremy.trammell at setaris.com> wrote:
>   
>> Hello...
>>
>> I'm trying to build an MFC GUI for libpurple and after finally managing to
>> get it built (using the excellent winpidgin-build-fetcher.sh script) I build
>> the nullclient and ran it.  If I connect to Yahoo, all goes as expected and
>> I can receive messages from others on the network.  If I select AIM, it only
>> makes if through the first two steps of the connection process ("0 of 6
>> Connecting" and "1 of 6 Username sent").  The pidgin client has no such
>> issue.  I'm running with debug set to TRUE, and other then the file write
>> errors from the default '/dev/null' file path, no further messages are
>> produced.  Any thoughts?
>>     
>
> Did you override the default glib io handlers (like is done in
> pidgin/gtkeventloop.c)?
>
> -D
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pidgin.im/pipermail/support/attachments/20090707/e0351757/attachment.html>