TQt4 port koffice

This should enable compilation under both Qt3 and Qt4; fixes for any missed components will be forthcoming


git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/applications/koffice@1238284 283d02a7-25f6-0310-bc7c-ecb5cbfe19da

1 files changed, 8 insertions, 8 deletions

diff --git a/kexi/kexiutils/tristate.h b/kexi/kexiutils/tristate.h
index a3de22bb..0a8df95c 100644
--- a/kexi/kexiutils/tristate.h
+++ b/kexi/kexiutils/tristate.h
@@ -20,7 +20,7 @@
 #ifndef _TRISTATE_TYPE_H_
 #define _TRISTATE_TYPE_H_
 
-#include <qstring.h>
+#include <tqstring.h>
 
 /**
  * \e cancelled value, in most cases usable if there is a need for returning 
@@ -79,7 +79,7 @@ static const char dontKnow = cancelled;
  * is irrelevant to the current situation.
  *
  * Other use for tristate class could be to allow cancellation within 
- * a callback function or a Qt slot. Example:
+ * a callback function or a TQt slot. Example:
  * \code
  * public slots:
  *   void validateData(tristate& result);
@@ -87,10 +87,10 @@ static const char dontKnow = cancelled;
  * Having the single parameter, signals and slots have still simple look.
  * Developers can alter their code (by replacing 'bool& result' with 'tristate& result')
  * in case when a possibility of canceling of, say, data provessing needs to be implemented.
- * Let's say \e validateData() function uses a QDialog to get some validation from a user.
- * While QDialog::Rejected is returned after cancellation of the validation process, 
+ * Let's say \e validateData() function uses a TQDialog to get some validation from a user.
+ * While TQDialog::Rejected is returned after cancellation of the validation process, 
  * the information about cancellation needs to be transferred up to a higher level of the program.
- * Storing values of type QDialog::DialogCode there could be found as unreadable, and
+ * Storing values of type TQDialog::DialogCode there could be found as unreadable, and
  * casting these to int is not typesafe. With tristate class it's easier to make it obvious that 
  * cancellation should be taken into account. 
  *
@@ -163,10 +163,10 @@ public:
 	/**
 	 * \return text representation of the value: "true", "false" or "cancelled".
 	 */
-	QString toString() const {
+	TQString toString() const {
 		if (m_value==False)
-			return QString::fromLatin1("false");
-		return m_value==True ? QString::fromLatin1("true") : QString::fromLatin1("cancelled");
+			return TQString::tqfromLatin1("false");
+		return m_value==True ? TQString::tqfromLatin1("true") : TQString::tqfromLatin1("cancelled");
 	}
 
 private: