rename the following methods:

tqparent parent
tqmask mask


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

2 files changed, 6 insertions, 6 deletions

diff --git a/kommander/examples/current/kpartmwframe.kmdr b/kommander/examples/current/kpartmwframe.kmdr
index cdd17f53..7d15aecf 100755
--- a/kommander/examples/current/kpartmwframe.kmdr
+++ b/kommander/examples/current/kpartmwframe.kmdr
@@ -95,7 +95,7 @@ _loadup = 2
                                 <stringlist>
                                     <string>#!kommander
 if widgetExists("ScriptObject13") then
-  TextBrowser1.setText("This text was written by a script on the tqparent frame window. It could have been a dialog, but we chose to illustrate with a MainWindow for this demo.")
+  TextBrowser1.setText("This text was written by a script on the parent frame window. It could have been a dialog, but we chose to illustrate with a MainWindow for this demo.")
   ScriptObject13.execute
 else
   message_error("You do not have the KPart child dialog loaded")
diff --git a/kommander/examples/current/kpartpart.kmdr b/kommander/examples/current/kpartpart.kmdr
index 11b6a806..26e4171c 100755
--- a/kommander/examples/current/kpartpart.kmdr
+++ b/kommander/examples/current/kpartpart.kmdr
@@ -42,11 +42,11 @@
             </property>
             <property name="text">
                 <string>You can click the test button to insert text
-If you are loaded in the tqparent frame you can click the rocket icon on the toolbar or use the function menu to select "Talk to KPart". 
+If you are loaded in the parent frame you can click the rocket icon on the toolbar or use the function menu to select "Talk to KPart". 
 
-Any Kommander program can be run as a KPart. You need the KPart plugin to load KParts. Note that running Kommander programs as KParts is not without risks. For one thing you loose DCOP in the tqparent and the old parser ceases to work. Additionally since all widgets are accecssible from the tqparent and duplicate widget name can cause a Kommander lock up. 
+Any Kommander program can be run as a KPart. You need the KPart plugin to load KParts. Note that running Kommander programs as KParts is not without risks. For one thing you loose DCOP in the parent and the old parser ceases to work. Additionally since all widgets are accecssible from the parent and duplicate widget name can cause a Kommander lock up. 
 
-Because of all this and the fact that the Actions on the unsupported MainWindow are incompatible it is impossible for the child to talk with the tqparent. On this dialog we use a timer on the tqparent polling the child for requests every 100 ms. It's a crude hack but it does yield acceptable behavior. 
+Because of all this and the fact that the Actions on the unsupported MainWindow are incompatible it is impossible for the child to talk with the parent. On this dialog we use a timer on the parent polling the child for requests every 100 ms. It's a crude hack but it does yield acceptable behavior. 
 
 This demo is intended to run both kpartwmframe.kmdr and kpartpart.kmdr. </string>
             </property>
@@ -97,7 +97,7 @@ endif
 if _LOADED == true then
   kpmessage.setText("You have mail")
 else
-  message_info("this only works when loaded as a KPart in it's tqparent window")
+  message_info("this only works when loaded as a KPart in it's parent window")
 endif
 </string>
                         </stringlist>
@@ -122,7 +122,7 @@ endif
                     </property>
                     <property name="associations" stdset="0">
                         <stringlist>
-                            <string>message_info("We just got a message from our tqparent frame!", "Parent called Child")</string>
+                            <string>message_info("We just got a message from our parent frame!", "Parent called Child")</string>
                         </stringlist>
                     </property>
                 </widget>