-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Export map level scale based dependencies in most vector symbology #3436
Conversation
@m-kuhn, took a while to get the build going, but should be good for review now :-) |
@@ -263,7 +263,7 @@ class CORE_EXPORT QgsFeatureRenderer | |||
Q_DECL_DEPRECATED virtual QDomElement writeSld( QDomDocument& doc, const QgsVectorLayer &layer ) const; | |||
//! create the SLD UserStyle element following the SLD v1.1 specs with the given name | |||
//! @note added in 2.8 | |||
virtual QDomElement writeSld( QDomDocument& doc, const QString& styleName ) const; | |||
virtual QDomElement writeSld( QDomDocument& doc, const QString& styleName, QgsStringMap props = QgsStringMap() ) const; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this is an api break it will need to be documented in the doc/api_break.dox file (and also unfortunately makes the commit ineligible for backporting)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We discussed the approach a bit during the FOSS4G code sprint, because I wanted to keep this one backportable. I probably have misunderstood (limited c++ experience), what if I use another method in overload, would that make the patch backportable instead?
For the benefit of my understanding, what makes the current approach non backportable? Since the parameter has a default value, it would seem it's transparent to a source compile, but I'm guessing it's maybe not binary compatible?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It changes the API because it's virtual, so any override of it will no longer match in signature.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @m-kuhn. Would adding a parallel method with the extra argument be any better? I guess its default implementation would just call onto the older version. And all existing subclasses would override the new method, in order to get the scale ranges and encode them in the rules.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the 3.0 version I like the current approach.
But for a backported version this should be ok.
Pull request updated, backwards incompatible change documented. |
Thanks a lot |
Thank you @m-kuhn. Before leaving FOSS4G me and @raymondnijssen discussed about the text symbolizer, the plan was that he was going to make a pull request with what he had (incomplete, but functional enough) and then we can work on it toghether. I also told him to contact me directly for any help regarding TextSymbolizer. So, everything already in motion :-) |
I've seen the symbolizer in action. And a picture from Raymond on On 01/09/16 14:09, Andrea Aime wrote:
|
This one solves https://hub.qgis.org/issues/15428