On Monday 27 March 2017 09:22:09 Philippe wrote: > > (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.
Good. But only one paint engine is enough to make a cross-platform API lie. Grepping a bit, QAlphaPaintEngine::drawPolygon() is particularly inefficient. Thanks, Marc -- Marc Mutz <[email protected]> | Senior Software Engineer KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company Tel: +49-30-521325470 KDAB - The Qt, C++ and OpenGL Experts _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
