summaryrefslogtreecommitdiffstats
path: root/lib/kofficecore/THOUGHTS
diff options
context:
space:
mode:
Diffstat (limited to 'lib/kofficecore/THOUGHTS')
-rw-r--r--lib/kofficecore/THOUGHTS4
1 files changed, 2 insertions, 2 deletions
diff --git a/lib/kofficecore/THOUGHTS b/lib/kofficecore/THOUGHTS
index fc936fdc..f0121aa9 100644
--- a/lib/kofficecore/THOUGHTS
+++ b/lib/kofficecore/THOUGHTS
@@ -30,7 +30,7 @@ solve zooming and "scrolling" problems.
One ugly problem also is what we will do about performance problems on
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
+that we *always* repaint the whole area, no matter what. This can easily be
optimized to a WNorthWestGravity like behavior, because you can't edit those
embedded parts anyway, so even kchart and other non-WNG apps support that.
( we have to translate the painter, of course).
@@ -44,7 +44,7 @@ whether they are the root views (not embedded), or they are
*active* embedded views. There only has to be a KoView object.
There is *one* zoom factor for both axes (x/y) and the whole
-content (text, objects, tqchildren,...) is zoomed accordingly.
+content (text, objects, children,...) is zoomed accordingly.
This kind of zooming is like the zoom support you know from
other applications.