summaryrefslogtreecommitdiffstats
path: root/doc/man/man3/tqwidget.3qt
diff options
context:
space:
mode:
Diffstat (limited to 'doc/man/man3/tqwidget.3qt')
-rw-r--r--doc/man/man3/tqwidget.3qt2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/man/man3/tqwidget.3qt b/doc/man/man3/tqwidget.3qt
index 456e74284..dbba2636e 100644
--- a/doc/man/man3/tqwidget.3qt
+++ b/doc/man/man3/tqwidget.3qt
@@ -1802,7 +1802,7 @@ This event handler can be reimplemented in a subclass to receive paint events.
.PP
A paint event is a request to repaint all or part of the widget. It can happen as a result of repaint() or update(), or because the widget was obscured and has now been uncovered, or for many other reasons.
.PP
-Many widgets can simply repaint their entire surface when asked to, but some slow widgets need to optimize by painting only the requested region: QPaintEvent::region(). This speed optimization does not change the result, as painting is clipped to that region during event processing. QListView and QCanvas do this, for example.
+Many widgets can simply repaint their entire surface when asked to, but some slow widgets need to optimize by painting only the requested region: QPaintEvent::region(). This speed optimization does not change the result, as painting is clipped to that region during event processing. QListView and TQCanvas do this, for example.
.PP
Qt also tries to speed up painting by merging multiple paint events into one. When update() is called several times or the window system sends several paint events, TQt merges these events into one event with a larger region (see QRegion::unite()). repaint() does not permit this optimization, so we suggest using update() when possible.
.PP