Hi, Sorry for joining the discussion late - was on holidays until yesterday evening.
I am a +1 for removing the "render" checkbox - but first fix the case Denis has with labeling. If there are other issues besides that, I would also consider them a bug. Imagine if you had to freeze/unfreeze display in MS Office, Inkscape or Adobe Software - users would ask the devs to fix the rendering behaviour ... We have the second round of QGIS grants proposals. Would be a good project to submit to fix this issue. See http://blog.qgis.org/2017/02/19/qgis-grants-2-call-for-grant-proposals-2017/ - proposals should be submitted until March 19. I would assume that mapCanvas().setRenderFlag( False ) would still be possible for Python plugins to use, if the render checkbox would be removed. Andreas On 2017-02-28 22:33, Nyall Dawson wrote: > On 28 February 2017 at 15:36, Nyall Dawson <[email protected]> wrote: > >> Hi all, >> >> Was just chatting to Martin about this - and we both think it's time >> to drop the "render" checkbox from the status bar. >> >> This setting is a bit of a remnant from the pre-multithreaded >> rendering days. Now, there shouldn't be any benefit in switching it on >> ---- and if there is ----- there's a bug which we need to fix! >> >> There's not much code this saves, but it does help de-clutter the >> crowded status bar. >> >> Any objections?? Does anyone still need this checkbox? > > Ok - given the widespread support for this feature we'll consider this > a "won't fix"! > > Nyall > _______________________________________________ > 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
_______________________________________________ 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
