underdarkGIS’s Twitter Archive—№ 4,052

Good to know that is fixed now! Just ran into this issue in a class using 2.8/10 #QGIS @qgiswatch/652702837131055105