If you only want to learn about the configuration options, see Configure history.
The message history (or message log as it is often called) is usually the biggest part of the message window. It shows the ongoing conversation of an IM- or group chat session in chronological order. TabSRMM only implements a "split style" user interface where the message history shows the entire conversation in a scrollable window with the most recent (newest) event on the bottom. This is most widely accepted as a very intuitive solution and implemented as a default in most chat clients.
Customization can be an important factor here, because users tend to love features which allow them to take influence on the look of the message history. Because of this, TabSRMM supports many ways to display the history and the look of the conversation log can be customized in almost any way. Furthermore, it can even be replaced by other plugins which gives the user additional possibilities. The standard implementation of the message history is based on a Win32 Rich Edit text control, and, while powerful enough for most situations, it has some formatting limitations.
Basically, the message log can be displayed in 3 possible ways:
- The standard implementation. This is included in TabSRMM, no additional plugins are required.
- The IEView plugin. Requires the installation of the IEView plugin.
- The History++ plugin. This method uses the History++ plugin to display the message history.
Method 1) uses a Windows rich edit text control to implement the message log. It converts incoming and outgoing messages to formatted strings and builds a text document from these messages. This document is then sent to the text control for display. The advantages are:
- no additional plugin is required
- it is a relatively fast and resource friendly way of building the conversation log.
There are also some disadvantages, though:
- rich text format does not allow advanced formatting – e.g. background images or similar things.
- because the entire conversation is a single text document, it is not possible to select single message events once they have been sent to the log. You can only select and copy text like you can from any other text document in a Windows application.
Method 2) and 3) are using additional plugins (see above for more information). IEView allows almost any possible message log layout, because it is based on HTML and CSS. History++ is using a fixed layout, but allows to manipulate single events from the message history. It also makes your message log display in the message window consistent with the message history display.
How to configure which method should be used
Open the Miranda options dialog and navigate to Message Sessions → Log viewer which gives you the ability to choose from either Internal log (standard, included message history), IEView or History++.
Not all options may be available. The options to choose IEView or History++ are only available when these plugins are properly installed.
It is important to understand that whenever method 2) or 3) is used to display the history for any contact, most of the message log options in TabSRMM will not work. This applies to all formatting, fonts, colors, templates and other options concerning the message history display.
This is a common source of problems for new users. When installing and using either IEView or History++ to show the message history in TabSRMM, the user will have to configure these plugins instead of TabSRMM. Most message log options, listed in the configuration guide will not work, because the standard message history is disabled when IEView or History++ are enabled to render the message log.