Simple Status Message shouldn't replace "Options/Status/Status message" item

[GoogleCodeExporter]

In "Options/Status/Status message" option added by core is "Default messages", 
which can't be set in any other place. And it's used by other plugins too (some 
auto away plugins, etc.).

So Simple Status Message shouldn't replace that, or better, he should give 
opportunity to set these "Default messages".

Original issue reported on code.google.com by ROBYER on 18 Mar 2011 at 10:58

[GoogleCodeExporter]

Simple Status Message gives that opportunity. You can set "Use default message" 
for selected statuses (and protocol) if you want the core default messages or 
"Set the following message" if you want your own.

Original comment by dezred on 18 Mar 2011 at 11:35

• Added labels: Component-SimpleStatusMsg
• Removed labels: Component-

[GoogleCodeExporter]

Yes, but problem is that we can't change that "default messages". Of course its 
not unnecessarily for Simple Status Message as you said you can use "Set the 
following message", but problem is that "default messages" are used by some 
other plugins too - e.g. even Advanced Auto Away - ok, there is again option to 
"Set the following message" but isn't better to set "default messages" once for 
whole Miranda and then just use it in different plugins than set same message 
twice or more times again in different plugins?

Original comment by ROBYER on 18 Mar 2011 at 11:44

[GoogleCodeExporter]

That actually works correctly for global status changes (with the help of "Set 
the following message" which replaces "default message" - this change is 
visible for other plugins). SSM has more elaborate per-protocol status messages 
mechanism than the core status message module, which also means that default 
messages are stored in DB for each protocol, not only globally, and I think I 
can't do anything more for the compatibility with other plugins. They just have 
to support Simple Status Message to make some things work correctly...

Original comment by dezred on 18 Mar 2011 at 12:23

[GoogleCodeExporter]

Ok then :)

Original comment by ROBYER on 18 Mar 2011 at 12:34

[GoogleCodeExporter]

Original comment by dezred on 19 Mar 2011 at 12:37

• Changed state: Invalid