Status Message Retriever plugin

[pescuma]

This is a plugin that retrieves status messages based on timer and on status change. It is made for protocols that store the status message at the client, like ICQ does.

Please, do not enable this for MSN nor Jabber, because it can cause bad side effects (these protocols handle status message internally and smr can break things).


Download:
--------------
DLL: http://pescuma.mirandaim.ru/miranda/smr.zip
Sources: SVN at https://developer.berlios.de/projects/mgoodies/


Changelog:
---------------

. 1.0.0.7
* Fix for crash

. 1.0.0.6
* Fix for crash at startup

. 1.0.0.5
* Now uses tabs from core in options
* Options are now expert only

. 1.0.0.4
+ Added support for Miranda 0.8

. 1.0.0.3
* Fix for services
+ Added more info text

. 1.0.0.2
+ If XStatus name and message are the same, show only one (and not Name: message)

. 1.0.0.1
* Try to fix bug on thread finish
+ Don't check contacts on invisible list
+ Options in XP style

. 1.0.0.0
* Only save retrieved status message if needed
+ Langpack file
+ Changed version number to reflect that the plugin is ready

. 0.0.1.6
* Bugfix to freezing

. 0.0.1.5
* Bugfix in poll
* Bugfix in xstatus code

. 0.0.1.4
+ Deal with XStatus
* Tabbed options dialog

. 0.0.1.3
+ Option to always clear status message
* Fixed error detection
* Online check if check on timer enabled also

. 0.0.1.2
+ New logic to handle requests. Should work better for ICQ, but messages will take longer to arrive.

. 0.0.1.1
+ Updater support
+ More options
+ A lot of changes in pooling code
* Bugfix in contact menu option

. 0.0.1.0
+ Initial version

[akustyk]

Hello Pescuma,

How about a plugin that unifies all this change things. I mean, a "change notifier" that show us when status messages, nickname or xstatuses were changed.

I think this will save memory and will be more efficient than several separated plugins.

Just an idea..

[Great-er]

No, i disagree, maybe you could ask the author of smcn to do this, but i do like the idea of this small, stable plugin which does just that, and not more. anyway, why add nickname or xstatuses when this plugin is for status messages?

@pescuma: seems to be running stable and doing what is should here. very handy. thanks!

[gerk]

although it's currently off-topic: I like the idea of one Ultimate Status Notify plugin (so its name is already born ;-) that's an idea I also had some time ago... reason: normal status, xstatus and status msgs often kinda interact.

for example I don't want to see normal status notifications for a contact that has currently set an XStatus, another example: in case of a status change I only want one popup that informs me about the new status AND the status msg, currently it's not possible to disable the smcn popup in this case, so I get two popups, one from the status notify plugin and one from smcn...

furthermore all current status notify plugins (NewStatusNotify, XStatusNotify and ContactsStatusNotify) have got disadvantages. XStatusNotify popups always come with delay (why?), they show up before XStatusName and XStatus Msg have been retrieved so at first they always show those standard xstatus descriptions, which do not interest me at all.
all three plugins do not allow to fully customize popups texts from inside miranda options and do not support several variables for this purpose, e.g. for new/old status, for new/old status msg and for new/old XStatus/XStatusMsg.
the two normal status notify plugins currently do not care of the contacts' previous status, so popup texts like "contact signed on" are currently impossible (contacts status notify claims to be able to do so, but the feature doesn't work).
so I'd be one more supporter of the idea, because of the mentioned interaction... but we cannot force pescuma to do anything, so let's wait for his opinion...

[pescuma]

I think that this should be discussed in SMCN thread and not here. SMR will not notify of anything.

Now the off-topic: I do think it is a good idea to join all those notification plugins, but I really wont be able to do that because of time (I have other priorities in mind). Maybe in future or some other developer could do it.

[gerk]

yes, of course SMR is not meant to notify of anything... but you will as well release a new improved version of SMCN only for the status msg change notify purpose, won't you? :-)

[pescuma]

I intend to remove from smcn the smr code... But i dont know how further i'll go with the changes... This is yet to be decided...

[pescuma]

. 0.0.1.1
+ Updater support
+ More options
+ A lot of changes in pooling code
* Bugfix in contact menu option

[andrewabc]

So what exactly is the difference between this and SMCN?
I only use jabber and msn protocol. Is this [better] for ICQ users?

This is a plugin that pool status messages at a specified interval.

What does pool messages mean?

Using msn and SMCN it tells me that someone changed their status message a second or two after they change it. How is this plugin different?

[pescuma]

So what exactly is the difference between this and SMCN?
I only use jabber and msn protocol. Is this [better] for ICQ users?

What does pool messages mean?

This is intended for ICQ users. MSN store status messages at the server and notify everyone when one changes, so the status message you see is always the last one set by that contact. ICQ store the messages at the clients, so you have to request it to your contact.

What this plugin do is request the status message from the contacts of a protocol at a certain interval (it pool the contacts, requesting its messages).

I dont know Jabber, but for MSN you do not need this.

Using msn and SMCN it tells me that someone changed their status message a second or two after they change it. How is this plugin different?

SMCN originally only had notification code. Later, slotwin added code to pool the status messages (i request that and he did - ps thanks, slotwin). So SMCN now does 2 things: pool messages and notify of changes.

I decided now to split this functions in two plugins: SMR will only pool messages and SMCN will only notify status messages. So, they will be totaly independent.

I hope I could explain this ;-)