summaryrefslogtreecommitdiffstats
path: root/doc/html/coordsys.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/html/coordsys.html')
-rw-r--r--doc/html/coordsys.html10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/html/coordsys.html b/doc/html/coordsys.html
index 1b497fa9..e6ed92dd 100644
--- a/doc/html/coordsys.html
+++ b/doc/html/coordsys.html
@@ -34,7 +34,7 @@ body { background: #ffffff; color: black; }
<p> A <a href="ntqpaintdevice.html">paint device</a> in TQt is a drawable 2D
-surface. <a href="ntqwidget.html">TQWidget</a>, <a href="ntqpixmap.html">TQPixmap</a>, <a href="ntqpicture.html">TQPicture</a> and <a href="ntqprinter.html">TQPrinter</a> are all
+surface. <a href="tqwidget.html">TQWidget</a>, <a href="ntqpixmap.html">TQPixmap</a>, <a href="ntqpicture.html">TQPicture</a> and <a href="ntqprinter.html">TQPrinter</a> are all
paint devices. A <a href="ntqpainter.html">TQPainter</a> is an object which can draw on such
devices.
<p> The default coordinate system of a paint device has its origin at the
@@ -76,15 +76,15 @@ or two ints, for example <a href="ntqpainter.html#drawPoint">TQPainter::drawPoin
<td valign="top">A single 2D vector. Internally, TQPoint and <a href="ntqsize.html">TQSize</a> are the same,
but a point is not the same as a size, so both classes exist.
Again, most functions accept either a TQSize or two ints, for
-example <a href="ntqwidget.html#resize">TQWidget::resize</a>().
+example <a href="tqwidget.html#resize">TQWidget::resize</a>().
<tr bgcolor="#f0f0f0"> <td valign="top"><a href="ntqrect.html">TQRect</a>
<td valign="top">A 2D rectangle. Most functions accept either a <a href="ntqrect.html">TQRect</a> or four
-ints, for example <a href="ntqwidget.html#setGeometry">TQWidget::setGeometry</a>().
+ints, for example <a href="tqwidget.html#setGeometry">TQWidget::setGeometry</a>().
<tr bgcolor="#d0d0d0"> <td valign="top"><a href="ntqregion.html">TQRegion</a>
<td valign="top">An arbitrary set of points, including all the normal set
operations, e.g. <a href="ntqregion.html#intersect">TQRegion::intersect</a>(), and also a less
usual function to return a list of rectangles whose union is
-equal to the region. <a href="ntqregion.html">TQRegion</a> is used e.g. by <a href="ntqpainter.html#setClipRegion">TQPainter::setClipRegion</a>(), <a href="ntqwidget.html#repaint">TQWidget::repaint</a>() and <a href="qpaintevent.html#region">TQPaintEvent::region</a>().
+equal to the region. <a href="ntqregion.html">TQRegion</a> is used e.g. by <a href="ntqpainter.html#setClipRegion">TQPainter::setClipRegion</a>(), <a href="tqwidget.html#repaint">TQWidget::repaint</a>() and <a href="qpaintevent.html#region">TQPaintEvent::region</a>().
<tr bgcolor="#f0f0f0"> <td valign="top"><a href="ntqpainter.html">TQPainter</a>
<td valign="top">The class that paints. It can paint on any device with the
same code. There are differences between devices, <a href="ntqprinter.html#newPage">TQPrinter::newPage</a>() is a good example, but <a href="ntqpainter.html">TQPainter</a> works the
@@ -117,7 +117,7 @@ is what's usually called projection in 3D.)
<p> The third step uses the viewport. The viewport too, describes the view
boundaries, but in device coordinates. The viewport and the windows
describe the same rectangle, but in different coordinate systems.
-<p> On-screen, the default is the entire <a href="ntqwidget.html">TQWidget</a> or <a href="ntqpixmap.html">TQPixmap</a> where
+<p> On-screen, the default is the entire <a href="tqwidget.html">TQWidget</a> or <a href="ntqpixmap.html">TQPixmap</a> where
you are drawing, which is usually appropriate. For printing this
function is vital, since very few printers can print over the entire
physical page.