diff options
Diffstat (limited to 'doc/man/man3/qcanvaspolygonalitem.3qt')
| -rw-r--r-- | doc/man/man3/qcanvaspolygonalitem.3qt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/man/man3/qcanvaspolygonalitem.3qt b/doc/man/man3/qcanvaspolygonalitem.3qt index f622d5130..8d4176283 100644 --- a/doc/man/man3/qcanvaspolygonalitem.3qt +++ b/doc/man/man3/qcanvaspolygonalitem.3qt @@ -74,7 +74,7 @@ The QCanvasPolygonalItem class provides a polygonal canvas item on a QCanvas. .PP The mostly rectangular classes, such as QCanvasSprite and QCanvasText, use the object's bounding rectangle for movement, repainting and collision calculations. For most other items, the bounding rectangle can be far too large -- a diagonal line being the worst case, and there are many other cases which are also bad. QCanvasPolygonalItem provides polygon-based bounding rectangle handling, etc., which is much faster for non-rectangular items. .PP -Derived classes should try to define as small an area as possible to maximize efficiency, but the polygon must \fIdefinitely\fR be contained completely within the polygonal area. Calculating the exact retquirements is usually difficult, but if you allow a small overestimate it can be easy and tquick, while still getting almost all of QCanvasPolygonalItem's speed. +Derived classes should try to define as small an area as possible to maximize efficiency, but the polygon must \fIdefinitely\fR 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 all of QCanvasPolygonalItem's speed. .PP Note that all subclasses \fImust\fR call hide() in their destructor since hide() needs to be able to access areaPoints(). .PP |