received-im-msg signal - no conversation

Etan Reisner pidgin at
Sun Oct 18 18:53:29 EDT 2009

On Fri, Sep 25, 2009 at 10:48:45AM +0200, mowsen wrote:
> the problem now is, that $conv is empty. after sending a second
> message from the same sender $conv exists. how can i close the
> conversation right after the first received message?

received-im-msg fires before the conversation window is created on the
first message in a new conversation, you can use the gtkconv
displayed-im-msg signal to catch it later (though that will catch both
incoming and outgoing messages so you'll need to watch for that) or set up
a short timer to destroy the conversation after the signal has finished
being processed and libpurple has created the conversation.

> thanks alot,
> mowsen


More information about the Devel mailing list