On mercredi 15 novembre 2017 16:18:29 CET Matthias Kuhn wrote: > Hi Even, > > we have shortly discussed this topic in the past and the general > consensus was, not to offer such an option (which is easy to forget and > hard to set right without deep knowledge). > > Should we consider a `virtual QgsDataProvider::renderInPreview()` > method, that can be finetuned by each provider and has a default > implementation that either uses rendering times as heuristics
So if the provider of one layer returns false in renderInPreview() that would disable the rendering of those layers in the preview images ? > or just blacklists some known-expensive types? The provider has not necessarily that knowledge. In my example, if you are very close to the server and have high bandwidth, preview jobs wouldn't be a bottleneck. Or there are cases like JPEG2000 where the CPU speed and number of cores can make a huge difference, so the knowledge of the GDAL driver isn't enough. So I'm wondering if just a per-layer timing logic in QgsMapRendererCustomPainterJob::doRender() wouldn't be enough. -- Spatialys - Geospatial professional services http://www.spatialys.com
_______________________________________________ QGIS-Developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
