summaryrefslogtreecommitdiffstats
path: root/doc/html/qcanvaspolygonalitem.html
diff options
context:
space:
mode:
authorTimothy Pearson <kb9vqf@pearsoncomputing.net>2013-05-07 21:58:34 -0500
committerTimothy Pearson <kb9vqf@pearsoncomputing.net>2013-05-07 21:58:34 -0500
commitc740211ffba3330d951f4c3ddefea8edf23a01cd (patch)
tree0a8b7641d3c5b576d18a2f7912c75fc600f494e2 /doc/html/qcanvaspolygonalitem.html
parent8a4eacb6185de3653f6ae401c352aef833a9e72a (diff)
downloadtqt3-c740211ffba3330d951f4c3ddefea8edf23a01cd.tar.gz
tqt3-c740211ffba3330d951f4c3ddefea8edf23a01cd.zip
Automated update from Qt3
Diffstat (limited to 'doc/html/qcanvaspolygonalitem.html')
-rw-r--r--doc/html/qcanvaspolygonalitem.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/html/qcanvaspolygonalitem.html b/doc/html/qcanvaspolygonalitem.html
index 093517610..b9f74003f 100644
--- a/doc/html/qcanvaspolygonalitem.html
+++ b/doc/html/qcanvaspolygonalitem.html
@@ -80,7 +80,7 @@ handling, etc., which is much faster for non-rectangular items.
to maximize efficiency, but the polygon must <em>definitely</em> be
contained completely within the polygonal area. Calculating the
exact requirements is usually difficult, but if you allow a small
-overestimate it can be easy and tquick, while still getting almost
+overestimate it can be easy and quick, while still getting almost
all of TQCanvasPolygonalItem's speed.
<p> Note that all subclasses <em>must</em> call <a href="qcanvasitem.html#hide">hide</a>() in their destructor
since hide() needs to be able to access <a href="#areaPoints">areaPoints</a>().