1.0 is out

Today, I uploaded tabSRMM 1.0.0.0 to the Miranda file listing (also known as the addons page).

Both Unicode and ANSI versions are available now. They require Miranda 0.5.0.0, although the ANSI version should run on 0.4.x.x (but that is an unsupported configuration).

The DLLs are built with Visual C++ 6.0, so no additional libraries are required.
The default icon pack is included as well.

The "plan" for future developments

tabSRMM 1.0.0.x will be feature frozen from now on. This means, the 1.0.0.x branch will only get bug fixes but no new features. It will also be kept compatible with the Miranda 0.5 series.

New features will go in the trunk code (which currently has a version number of 1.1.0.6).

For a list of changes you can view the included changelog or search this blog. There is also the forum where you can find a lot more additional informations.

Known issues in that build

• some minor formatting problems are still left in auto - bidirectional mode, although, the current code has much improved. Almost all formatting options, including grid lines and mutliple background colors, are again working and most visual artifacts (wrong background colors etc.) should no longer appear.
• when using auto-bidi mode, the last message will show an additional newline. This is not avoidable, because otherwise the rich edit control won't properly format the last message in the history.
• Disconnecting from IRC while multiple group chat windows or tabs are still open may lead to a crash. That may also happen on exit, so I suggest that you first close all containers before you exit Miranda. This is currently under investigation as it is not clear whether it is a problem in IRC or tabSRMM (or maybe both).
• Skinning should still be considered alpha quality code. It works well for many people, but there are minor issues.
• Same goes for message splitting. It basically works, but there are issues which are beyond my control (e.g. it doesn't work with ICQ offline messages since the ICQ protocol does not report the proper message size limit when a contact is offline).