Fix a number of strings in Trinity that were incorrectly converted to TQ* from Q*

This fixes the Kopete MSN protocol among other things


git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/applications/kvirc@1254372 283d02a7-25f6-0310-bc7c-ecb5cbfe19da
v3.5.13-sru
tpearson 13 years ago
parent be1a164c88
commit 10ff1b477b

@ -856,7 +856,7 @@ void KviIrcContext::terminateConnectionRequest(bool bForce,const TQString &szQui
KviTQCString dat = console()->encodeText(buffer);
bWasSentQuit = false;
connection()->stateData()->setSentQuit();
connection()->sendFmtData("TQUIT :%s",dat.data() ? dat.data() : ""); // here theoretically we COULD get disconnected
connection()->sendFmtData("QUIT :%s",dat.data() ? dat.data() : ""); // here theoretically we COULD get disconnected
} // else it was already sent anyway
if(KVI_OPTION_BOOL(KviOption_boolForceBrutalQuit) || bWasSentQuit || bForce)

@ -884,7 +884,7 @@ namespace KviKvsCoreCallbackCommands
[comment]# We don't wait anymore :)[/comment]
%:state++
echo "Sending TQUIT..."
return "TQUIT$cr$lf"
return "QUIT$cr$lf"
}
break;
default:

@ -1425,7 +1425,7 @@ void KviServerParser::parseNumericNoSuchNick(KviIrcMessage *msg)
}
}
// FIXME: #warning "KVI_OUT_NOSUCHNICKCHANNEL ?"
// FIXME: #warning "TQUERIES SHOULD REPORT NO TARGET HERE! (?)"
// FIXME: #warning "QUERIES SHOULD REPORT NO TARGET HERE! (?)"
if(!msg->haltOutput())
{
KviWindow * pOut = (KviWindow *)(msg->connection()->findQuery(szNick));

@ -34,7 +34,7 @@ KviLiteralMessageParseStruct KviServerParser::m_literalParseProcTable[]=
{ "TOPIC" , PTM(parseLiteralTopic) },
{ "JOIN" , PTM(parseLiteralJoin) },
{ "PART" , PTM(parseLiteralPart) },
{ "TQUIT" , PTM(parseLiteralQuit) },
{ "QUIT" , PTM(parseLiteralQuit) },
{ "NICK" , PTM(parseLiteralNick) },
{ "KICK" , PTM(parseLiteralKick) },
{ "NOTICE" , PTM(parseLiteralNotice) },

@ -79,7 +79,7 @@ KviConnectionOptionsWidget::KviConnectionOptionsWidget(TQWidget * parent)
"that was <b>not requested by the user</b> by the means of the TQUIT message." \
"<p><b>Warning:</b> If you use /RAW to send a TQUIT message to the server, " \
"this option will not behave correctly, since does not detect the outgoing " \
"TQUIT message and will attempt to reconnect after the server has closed the connection. " \
"QUIT message and will attempt to reconnect after the server has closed the connection. " \
"For this reason, always use the /TQUIT command to close your connections. " \
"This option may also behave incorrectly with bouncers that support " \
"detaching, in this case a solution could be to prepare an alias that sends the " \

Loading…
Cancel
Save