comparison plugins/SIGNALS @ 3517:6b0cb60162f4

[gaim-migrate @ 3590] Rob McQueen added a mute feature to his nice little docklet. I added a queuing feature. Configure the docklet in the plugins dialog to queue unread messages, and when you receive a message the docklet will eat it up and show a little message pending icon. Click on it, and read your message. ICQ people will like it. I also made plugin_event use a va_list. I bet this breaks perl. committer: Tailor Script <[e-mail]>

3516:db00eb77997d

	event_im_displayed_sent,
	event_im_displayed_rcvd,
	event_chat_send_invite,
	event_got_typing,
	event_del_conversation,
};

To add a signal handler, call the fuction gaim_signal_connect with the
following arguments:

	you set *what to NULL the message won't be sent, but the preferred
	way of doing this is to attach to event_im_send so that it really
	won't be displayed at all.

event_im_displayed_rcvd:
	struct gaim_connection *gc, char *who, char *what, guint32 flags

	This is called after what you receive is displayed. This is useful
	for displaying an autoresponse after the message that triggered it.
	There are a bunch of things that are odd about this, especially
	when dealing with being away, so be careful.

	'gc' is the connection the message was received on.
	'who' is who sent the message.
	'what' is what was sent.
	'flags' is flags on the message.

event_chat_send_invite:
	struct gaim_connection *gc, int id, char *who, char **msg

	This is called just before you're about to invite someone. It's

	notifications in direct IMs, and Yahoo can receive them any
	time.

	'gc' 	is the connection the typing is sent to.
	'who' 	is the person typing to you.
event_del_conversation:
	struct conversation *c

	This is called when a conversation window is closed.  It is
	called before any memory is deallocated so you are able to
	access any data related to the conversation without breaking
	anything.

	'c'	is he conversation being closed.

3517:6b0cb60162f4

	event_im_displayed_sent,
	event_im_displayed_rcvd,
	event_chat_send_invite,
	event_got_typing,
	event_del_conversation,
	event_connecting,
};

To add a signal handler, call the fuction gaim_signal_connect with the
following arguments:

	you set *what to NULL the message won't be sent, but the preferred
	way of doing this is to attach to event_im_send so that it really
	won't be displayed at all.

event_im_displayed_rcvd:
	struct gaim_connection *gc, char *who, char *what, guint32 flags, time_t time

	This is called after what you receive is displayed. This is useful
	for displaying an autoresponse after the message that triggered it.
	There are a bunch of things that are odd about this, especially
	when dealing with being away, so be careful.

	'gc' is the connection the message was received on.
	'who' is who sent the message.
	'what' is what was sent.
	'flags' is flags on the message.
	'time' is the time the message was received--it may be very different from the
	 time this signal gets called

event_chat_send_invite:
	struct gaim_connection *gc, int id, char *who, char **msg

	This is called just before you're about to invite someone. It's

	notifications in direct IMs, and Yahoo can receive them any
	time.

	'gc' 	is the connection the typing is sent to.
	'who' 	is the person typing to you.

event_del_conversation:
	struct conversation *c

	This is called when a conversation window is closed.  It is
	called before any memory is deallocated so you are able to
	access any data related to the conversation without breaking
	anything.

	'c'	is he conversation being closed.
	
event_connecting
	struct aim_user *u

	This is called when Gaim attempts to bring a user on-line. The
	boolean u->connecting is set to true, and a global counter
	incremented. The attempt can end with event_signon or event_signoff
	being called, depending upon whether the attempt was a sucess or
	a failure. In both cases, u->connecting is set to false and the
	counter decremented.
	
	'u'	is the account being connected