Translations:Plugin:TabSRMM/Tips/15/en: Difference between revisions

From Miranda NG
Jump to navigation Jump to search
(Importing a new version from external source)
 
(Importing a new version from external source)
 
Line 1: Line 1:
Some toolbar buttons have small arrows attached. Clicking these, opens a drop-down menu. The send button is one of these buttons, and when you open it, you get a menu with a few options. For example, you can enable/disable the multisend feature from there. Other options include:
Some toolbar buttons have small arrows attached. Clicking these, opens a drop-down menu. The send button is one of these buttons, and when you open it, you get a menu with a few options. For example, you can enable/disable the multisend feature from there. Other options include:
* '''Send without timeouts''' – when active, TabSRMM will not wait for an answer from the protocol when sending a message. This may resolve the annoying "Timeout" error messages when the other side is experiencing network or other problems. This entry is '''per contact''' and it will be saved to the database. There is no global option for this (and this is a good thing, because you shouldn't use this as a default – only use it for contacts which give you "Timeout" errors frequently). Note that you won't be informed when a message delivery fails, so enabling this options means that you'll never know whether a message has been delivered or not. If you want to have this globally, you need to setup it in the protocols options (most protocols offer a setting to disable sending confirmations).
* '''Send without timeouts''' – when active, TabSRMM will not wait for an answer from the protocol when sending a message. This may resolve the annoying "Timeout" error messages when the other side is experiencing network or other problems. This entry is per contact and it will be saved to the database. There is no global option for this (and this is a good thing, because you shouldn't use this as a default – only use it for contacts which give you "Timeout" errors frequently). Note that you won't be informed when a message delivery fails, so enabling this options means that you'll never know whether a message has been delivered or not. If you want to have this globally, you need to setup it in the protocols options (most protocols offer a setting to disable sending confirmations).

Latest revision as of 23:32, 26 September 2022

Information about message (contribute)
This message has no documentation. If you know where or how this message is used, you can help other translators by adding documentation to this message.
Message definition (Plugin:TabSRMM/Tips)
Some toolbar buttons have small arrows attached. Clicking these, opens a drop-down menu. The send button is one of these buttons, and when you open it, you get a menu with a few options. For example, you can enable/disable the multisend feature from there. Other options include:
* '''Send without timeouts''' – when active, TabSRMM will not wait for an answer from the protocol when sending a message. This may resolve the annoying "Timeout" error messages when the other side is experiencing network or other problems. This entry is per contact and it will be saved to the database. There is no global option for this (and this is a good thing, because you shouldn't use this as a default – only use it for contacts which give you "Timeout" errors frequently). Note that you won't be informed when a message delivery fails, so enabling this options means that you'll never know whether a message has been delivered or not. If you want to have this globally, you need to setup it in the protocols options (most protocols offer a setting to disable sending confirmations).

Some toolbar buttons have small arrows attached. Clicking these, opens a drop-down menu. The send button is one of these buttons, and when you open it, you get a menu with a few options. For example, you can enable/disable the multisend feature from there. Other options include:

  • Send without timeouts – when active, TabSRMM will not wait for an answer from the protocol when sending a message. This may resolve the annoying "Timeout" error messages when the other side is experiencing network or other problems. This entry is per contact and it will be saved to the database. There is no global option for this (and this is a good thing, because you shouldn't use this as a default – only use it for contacts which give you "Timeout" errors frequently). Note that you won't be informed when a message delivery fails, so enabling this options means that you'll never know whether a message has been delivered or not. If you want to have this globally, you need to setup it in the protocols options (most protocols offer a setting to disable sending confirmations).