Search results
Jump to navigation
Jump to search
Page title matches
- ...mb|<translate><!--T:1--> The red shaded part is usually called the message history or message log</translate>]] ...he configuration options, see [[Plugin:TabSRMM/Configure history|Configure history]].</translate>}}4 KB (680 words) - 02:08, 28 October 2022
- ...sage log.png|400px|thumb|The red shaded part is usually called the message history or message log]] ...he configuration options, see [[Plugin:TabSRMM/Configure history|Configure history]].}}4 KB (642 words) - 02:08, 28 October 2022
- The input history works like a LIFO (last in first out) stack. When you send a message it is ...window. Should you later open a new window for the same contact, the input history will still be available. All input histories will, however, be lost when yo3 KB (492 words) - 02:10, 28 October 2022
- ..." class="mw-content-ltr">The red shaded part is usually called the message history or message log</span>]] ...die Einstellungen ändern möchten, gehen Sie zu [[Plugin:TabSRMM/Configure history/de|Verlauf einrichten]].}}5 KB (739 words) - 02:09, 28 October 2022
- ...ard message log only. People using {{Plugin|IEView}} or {{Plugin|HistoryPP|History++}} to display the message log in TabSRMM can not use most of these options ...ions''' – message not directly related to the look and feel of the message history6 KB (958 words) - 02:08, 28 October 2022
- ...ard message log only. People using {{Plugin|IEView}} or {{Plugin|HistoryPP|History++}} to display the message log in TabSRMM can not use most of these options ...ions''' – message not directly related to the look and feel of the message history5 KB (904 words) - 02:09, 28 October 2022
- The input history works like a LIFO (last in first out) stack. When you send a message it is ...window. Should you later open a new window for the same contact, the input history will still be available. All input histories will, however, be lost when yo3 KB (466 words) - 02:10, 28 October 2022
- The input history works like a LIFO (last in first out) stack. When you send a message it is ...window. Should you later open a new window for the same contact, the input history will still be available. All input histories will, however, be lost when yo3 KB (538 words) - 02:11, 28 October 2022
- The input history works like a LIFO (last in first out) stack. When you send a message it is ...window. Should you later open a new window for the same contact, the input history will still be available. All input histories will, however, be lost when yo3 KB (562 words) - 02:11, 28 October 2022
- ...ard message log only. People using {{Plugin|IEView}} or {{Plugin|HistoryPP|History++}} to display the message log in TabSRMM can not use most of these options ...ions''' – message not directly related to the look and feel of the message history6 KB (987 words) - 02:09, 28 October 2022
Page text matches
- * History++ (.txt) * QIP 2005 history (.txt)326 bytes (39 words) - 21:28, 25 May 2019
- * History++ (.txt) * QIP 2005 history (.txt)321 bytes (40 words) - 21:26, 25 May 2019
- * History++ (.txt) * QIP 2005 history (.txt)328 bytes (39 words) - 21:27, 25 May 2019
- ...y contact or group chat at any time. Unlike {{Plugin|HistorySweeperLight}} history is never written to the database while using NoHistory.336 bytes (48 words) - 19:04, 10 October 2023
- ...y contact or group chat at any time. Unlike {{Plugin|HistorySweeperLight}} history is never written to the database while using NoHistory.336 bytes (48 words) - 19:04, 10 October 2023
- * History++ (.txt) * QIP 2005 history (.txt)386 bytes (47 words) - 21:26, 25 May 2019
- ...y contact or group chat at any time. Unlike {{Plugin|HistorySweeperLight}} history is never written to the database while using NoHistory.372 bytes (52 words) - 19:04, 10 October 2023
- * History++ (.txt) * QIP 2005 history (.txt)379 bytes (28 words) - 21:27, 25 May 2019
- History viewer for Miranda NG. ...age of the first event are displayed in special list. Moreover the part of history window is dedicated to contact list, so you can simply change it or use sea463 bytes (73 words) - 16:20, 26 December 2017
- == History ==572 bytes (49 words) - 20:05, 9 February 2022
- == History ==457 bytes (67 words) - 20:07, 9 February 2022
- History viewer for Miranda NG. ...age of the first event are displayed in special list. Moreover the part of history window is dedicated to contact list, so you can simply change it or use sea510 bytes (79 words) - 16:19, 26 December 2017
- == History ==454 bytes (65 words) - 20:05, 9 February 2022
- == History == <!--T:3-->604 bytes (87 words) - 20:05, 9 February 2022
- This plugin shows the history for a given contact using IEView. ...rrently useless. Consider another history viewer if you want a system wide history including authorization requests.1 KB (155 words) - 16:30, 19 February 2023
- This plugin shows the history for a given contact using IEView. ...rrently useless. Consider another history viewer if you want a system wide history including authorization requests.1 KB (155 words) - 16:30, 19 February 2023
- This plugin shows the history for a given contact using IEView. ...rrently useless. Consider another history viewer if you want a system wide history including authorization requests.1 KB (155 words) - 16:30, 19 February 2023
- ...age of the first event are displayed in special list. Moreover the part of history window is dedicated to contact list, so you can simply change it or use sea454 bytes (70 words) - 16:22, 26 December 2017
- ...age of the first event are displayed in special list. Moreover the part of history window is dedicated to contact list, so you can simply change it or use sea489 bytes (70 words) - 16:22, 26 December 2017
- ...age of the first event are displayed in special list. Moreover the part of history window is dedicated to contact list, so you can simply change it or use sea475 bytes (74 words) - 16:22, 26 December 2017