Adjusted to use new TQStringVariantMap type.

Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>

1 files changed, 3 insertions, 3 deletions

diff --git a/kjsembed/docs/ChangeLog b/kjsembed/docs/ChangeLog
index 49c861ea..c8e11eb3 100644
--- a/kjsembed/docs/ChangeLog
+++ b/kjsembed/docs/ChangeLog
@@ -78,7 +78,7 @@
 	in C++.  Conversions break down as follows:
 	TQStringList -> Array of javascript strings.
 	TQValueList<TQVariant> -> Array of Javascript values.
-	TQMap<TQString,TQVariant> -> Object/Array that has each TQString key as
+	TQStringVariantMap -> Object/Array that has each TQString key as
 		a property, and the TQVariant is mapped to a Javascript value.
 
 	From Javascript the conversions are a little different.
@@ -91,10 +91,10 @@
 		= convertToVariant( exec,  someArrayValue).toList();
 
 	Now if the Javascript value is a Javascript object or a map then
-	the conversion will go to a TQMap<TQString,TQVariant>.  An example of
+	the conversion will go to a TQStringVariantMap.  An example of
 	this would be like:
 	KJS::Value someJSObject;
-	TQMap<TQString,TQVariant> map = convertToVariant(exec,someJSObject)
+	TQStringVariantMap map = convertToVariant(exec,someJSObject)
 					.toMap();
 	TQString someVal = map["someProp"].toString();