> (the API is lying here, btw: QPainer::drawPolygon(const QPoint *, int) 
> suggests that you can manage the storage youself to avoid using the heap. But 
> you do that only to have the paint engine create something expensive as a 
> QPainterPath first chance it gets).

No heap allocation if you use the QPointF version with the raster engine.
Nor QPainterPath created with the raster engine.

Philippe

_______________________________________________
Development mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/development

Reply via email to