summaryrefslogtreecommitdiffstats
path: root/examples/opengl/overlay_x11/README.X11-OVERLAYS
diff options
context:
space:
mode:
Diffstat (limited to 'examples/opengl/overlay_x11/README.X11-OVERLAYS')
-rw-r--r--examples/opengl/overlay_x11/README.X11-OVERLAYS2
1 files changed, 1 insertions, 1 deletions
diff --git a/examples/opengl/overlay_x11/README.X11-OVERLAYS b/examples/opengl/overlay_x11/README.X11-OVERLAYS
index 4e7a9b647..18bcb1e5f 100644
--- a/examples/opengl/overlay_x11/README.X11-OVERLAYS
+++ b/examples/opengl/overlay_x11/README.X11-OVERLAYS
@@ -47,7 +47,7 @@ Given the above, a QGLWidget will by default use the main plane
visual, while all other widgets will use the overlay visual. Thus, one
can place a normal widget on top of the QGLWidget, and do drawing in
it, without destroying the image in the OpenGL window. In other words,
-one can use all the drawing capabilities of QPainter to draw the
+one can use all the drawing capabilities of TQPainter to draw the
annotations, rubberbands, whatever. For the typical use of overlays,
this is much easier than using OpenGL for rendering the annotations.