[Luga]

tabSRMM 0.9.9.100 available
_http://miranda.or.at/wp-content/uploads/2006/03/tabsrmm_unicode.zip

Changes made 2006-03-06
skin support for title bar buttons (set exact size and location)
loading a skin now also loads many visual settings, including tab text colors, avatar border color and more.
The container is now using an own window class and no longer the default dialog box window class.

Changes made 2006-03-06
fixed a few visual glitches with the toolbar and attached dropdown arrows
continued skinning engine - can now skin the window frame + title bar.
The message log history & message input box are now drawing their borders with visual style support. This avoids the “ugly” classic - style static edges around the text areas. Note that you can still set the text areas to display no border at all and appear completely flat (the option is on the Tabs and Layout page -> Message dialog visual settings -> Flat message log).

This also fixes a bug for WindowBlinds users where the static edge of the rich edit control shows “Garbage”.
fixed xStatus icon in the info panel - it does no longer depend on the “use_xicons” database setting (this setting does only control the xStatus icons on the tabs + window title).
fixed “sticky” xStatus icon on tabs when a contact goes offline or clears his xStatus



Changes made 2006-03-04
ability to show xStatus icons on the window titlebar and the tab(s). Note: this is a basically unsupported feature. To enable it, you must create a database entry, using dbeditor++

create a BYTE value under the Tab_SRMsg module, name it use_xicons and set the value to 1 (enable) or 0 (disable).
some tweaks to the new button drawing code for buttons with attached pulldown arrows.
added a new BBCode: and for strikethrough formatting. There is no button for this, and there won’t be any until the button bar gets its redesign with configurable button layout (planned for one of the next versions).

Changes made 2006-03-02

UI improvments

The toolbar has been slightly modified to allow configuration of button appearance. They can now be:
flat or 3d
themed (visual styled) or non-themed
You can set these options from Options->Message Window->Tabs and layout
Also, the “dropdown” buttons are no longer individual buttons, instead, the dropdown arrows are now “attached” to already existing buttons. This looks better and makes the extremely small dropdown buttons obsolete (they were looking pretty bad with some visual styles in non-flat mode).
The button tooltips have been enhanced and allow multiline tooltext display for better clearance.
changes to the window splitter (the small line just below the toolbar which splits the message window into the history and input area)

Now, when you release the splitter after moving it, a menu appears which allows you to select from a few options. Your selection will then determine what happens, and there are the following options:

Set Position for this Session -> default (and old behaviour), just set the splitter and it’s done. It will be saved when you close the session, unless you have disabled the “Autosave splitter” option on the splitter menu (see below, how to open this menu).
Set and Save for all Sessions -> will apply the new splitter position to all open message windows. It will also save it as default value for new message sessions.
Note will not set it for sessions which are using private splitter position. To check whether a message session is using a private (”per contact”) splitter position, click the leftmost dropdown arrow on the toolbar and choose the “Splitter” submenu.
Set and Save for this Contact only -> will save the splitter and set the splitter mode for this session to Private, which means that this contact will not share the splitter position with other message sessions.
Revert to old position -> will forget the changes and restore the position which was active before you were starting to drag the splitter.
added color (cyan) to the list of known colors for the [color] bbcode tag.
Workaround for UTF-8 sending bug(s) with Trillian - when the per contact send mode is set to “Force Ansi”, tabSRMM will write ProtoName/UnicodeSend and set this BYTE value to 0 before sending a message. If “Force Ansi” is not set, tabSRMM will clear this value when it exists.
ICQJ is using this DB value to disable UTF-8 sending on a “per contact” basis.



Changes made 2006-03-01 - (to be released with Alpha Build #49
fixed serious bug (possible crash/hangup) with the [color] bbcode and non-existant colornames.
fixed titlebar not updating in some situations.

Changes made 2006-01-28 - Alpha Build #48 released

(for changes see the CVS copy of the internal changlog.txt).