summaryrefslogtreecommitdiffstats
path: root/lib/kofficecore
diff options
context:
space:
mode:
authortpearson <tpearson@283d02a7-25f6-0310-bc7c-ecb5cbfe19da>2011-07-07 21:14:06 +0000
committertpearson <tpearson@283d02a7-25f6-0310-bc7c-ecb5cbfe19da>2011-07-07 21:14:06 +0000
commitafbfdc507bfaafc8824a9808311d57a9ece87510 (patch)
tree47be45bbd69c321ce79e14b683e59318748be9cb /lib/kofficecore
parent880d042b2902fae8007f202dd35ad9330499867b (diff)
downloadkoffice-afbfdc507bfaafc8824a9808311d57a9ece87510.tar.gz
koffice-afbfdc507bfaafc8824a9808311d57a9ece87510.zip
Rename incorrect instances of tqrepaint[...] to repaint[...]
git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/applications/koffice@1240369 283d02a7-25f6-0310-bc7c-ecb5cbfe19da
Diffstat (limited to 'lib/kofficecore')
-rw-r--r--lib/kofficecore/KoChild.h2
-rw-r--r--lib/kofficecore/THOUGHTS4
2 files changed, 3 insertions, 3 deletions
diff --git a/lib/kofficecore/KoChild.h b/lib/kofficecore/KoChild.h
index 64f41064..b79f6802 100644
--- a/lib/kofficecore/KoChild.h
+++ b/lib/kofficecore/KoChild.h
@@ -261,7 +261,7 @@ public:
virtual void setTransparent( bool transparent );
/**
- * It might be interesting for view updates and tqrepainting in general
+ * It might be interesting for view updates and repainting in general
* whether a child is transparent or not.
* @return true when this child is marked as transparent.
*/
diff --git a/lib/kofficecore/THOUGHTS b/lib/kofficecore/THOUGHTS
index 5d0a9338..33befa05 100644
--- a/lib/kofficecore/THOUGHTS
+++ b/lib/kofficecore/THOUGHTS
@@ -28,7 +28,7 @@ just agree that this QRect represents screen pixels at the given zoom value(s)
and the app can calculate the requested area to be painted itself. This should
solve zooming and "scrolling" problems.
One ugly problem also is what we will do about performance problems on
-tqrepainting a part. Some time ago we got a mail on KOffice where some guy
+repainting a part. Some time ago we got a mail on KOffice where some guy
asked what to do about making that embedded painting faster. The reason is
that we *always* tqrepaint the whole area, no matter what. This can easily be
optimized to a WNorthWestGravity like behavior, because you can't edit those
@@ -72,7 +72,7 @@ each axe here. (i.e. x/y zoom factors)
Related to that is child-panning. Indepenent of the zoom factor
the child shouldn't just show the left/top corner, but it should
-"remember" the position inside the document when it's tqrepainted
+"remember" the position inside the document when it's repainted
as inactive child.
###