Issue 61: FastPresences shouldn't send a presence if it's not going to make a change

Title	FastPresences shouldn't send a presence if it's not going to make a change
Priority	feature	Status	unread
Superseder		Nosy List	dmcc
Assigned To		Topics

Created on 2003-08-02.21:04:32 by dmcc, last changed 2003-08-02.21:04:32 by dmcc.

msg183 (view)

Author: dmcc

Date: 2003-08-02.21:04:32

For example: If you're already at show=None, status='',
typing 're' should not send a show=None, status=''.  When
FastPresences becomes a message processor, it should not
block  the 're' message in this case (normally, it would
cancel the 're' message and send a new presence instead).

History
Date	User	Action	Args
2003-08-02 21:04:32	dmcc	create

Issue61