On 7 February 2017 at 19:54, Paolo Cavallini <cavall...@faunalia.it> wrote: > Il 07/02/2017 10:53, Nyall Dawson ha scritto: > >> The issue here is that we potentially break existing projects. While >> updating the ui & api can be done, how can we handle user's data >> defined opacity/transparency rules? > > Aren't we breaking projects for q3 anyway?
Well, ideally not. Currently we only break projects which rely on very old features (such as 1.x labeling, conversion from old symbology, some composer features from maybe 2.6 or earlier). None of these breaks are ever likely to be encountered by users. But breaking data defined transparency may. Nyall > Cheers. > -- > Paolo Cavallini - www.faunalia.eu > QGIS & PostGIS courses: http://www.faunalia.eu/training.html > https://www.google.com/trends/explore?date=all&geo=IT&q=qgis,arcgis > _______________________________________________ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer _______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
