On Jun 9, 2007, at 2:47 PM, Patrick Ringl wrote:
> Hello Daniel,
>
> Daniel Henninger wrote:
>
>> The fact that the nickname is filled in here means that PyICQt is
>> sending
>> the nickname back to the client. Of course, it's up to the client to
>> decide what to do with that. (there's no way PyICQt can directly
>> modify
>> your roster to update the nickname in your actual roster)
>
> I am fully aware of that ;)
>
>> Typically a
>> client will receive the nickname, adjust it on screen, and send a
>> roster
>> update.
> Yup, of course it does. But what about the updateSSIContact?
>
> [2007-06-09 05:18:46] INFO :: [EMAIL PROTECTED] :: buddies.BuddyList ::
> updateSSIContact :: {'status': u'Idle 30 minutes - away.\n[Currently
> away]', 'presence': None, 'url': '', 'show': 'xa', 'ipaddr':
> '0.0.0.0',
> 'lanipport': 0L, 'nick': None, 'contact': 'xxxxxxx', 'lanipaddr':
> '0.0.0.0', 'icq2jid': <function icq2jid at 0x838109c>,
> 'icqprotocol': 9} ::
>
> Here nick is 'none' while contact shows the actual ICQ-UIN. I used
> pandion + miranda to test it .. and it's exactly the same
> behavior .. most of my contacts get an appropriate nickname .. the
> rest just shows the contact numbers. I doubt this is normal
> behavior, is it?
Actually it is. All that is is a call to the updateSSIContact
function which does a multitude of things. if you look at that
function itself, you'll see it only messages with the nickname if the
nickname is not null. So the call you are seeing isn't affecting the
nickname at all.
Daniel
>
>
> regards,
> Patrick
>
> _______________________________________________
> py-transports mailing list
> py-transports@blathersource.org
> http://lists.modevia.com/cgi-bin/mailman/listinfo/py-transports
_______________________________________________
py-transports mailing list
py-transports@blathersource.org
http://lists.modevia.com/cgi-bin/mailman/listinfo/py-transports
