On 9/2/19 12:02 PM, Sandro Santilli wrote:
On Sun, Sep 01, 2019 at 08:19:18AM +1000, Nyall Dawson wrote:
On Sat, 31 Aug 2019 at 17:02, Sandro Santilli <[email protected]> wrote:
It would sound like QgsProjectFileTransform::updateRevision should throw
an exception when unable to do what's been asked for ?
In this case QgsProjectFileTransform will be a red herring - there was
never a transform in place for this code, so there won't be any clues
there.
You mean QgsProjectFileTransform class never dealt with style configured in
project files ? Or what does "for this code" mean, exactly ?
Possibly. Sometimes there was/is legacy loading code directly inside the
readXml classes.
If you want to work on it now however, QgsProjectFileTransform sounds
like the path to go.
I reckon it was removed mainly because it cluttered the readXml code in
the classes.
Bests
Matthias
Regarding dropping backward compatibility, you say:
this was a wide group decision, with consensus from
all currently active QGIS developers and maintainers. It was deemed
unnecessary at this point in time.
Do you have a link to a mailing list thread where decision taking
process was conducted ? Just in case it has some hints about how
to fix this backward compatibility problem as QGIS moves forward.
--strk;
_______________________________________________
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
