-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
TopoViewer layer styles not honoured #31471
Comments
According to @nyalldawson from the mailing list the styles created with Convoluted process, but will have to be done for branches 3.4, 3.8 and master, in order to get a correctly styled TopoViewer layer group ... |
strk
added a commit
to strk/QGIS
that referenced
this issue
Aug 29, 2019
From 1.9 version to 2.18 version Closes qgis#31471
strk
added a commit
that referenced
this issue
Aug 29, 2019
From 1.9 version to 2.18 version Closes #31471
backporting bot
pushed a commit
that referenced
this issue
Aug 29, 2019
From 1.9 version to 2.18 version Closes #31471
backporting bot
pushed a commit
that referenced
this issue
Aug 29, 2019
From 1.9 version to 2.18 version Closes #31471
strk
added a commit
that referenced
this issue
Aug 29, 2019
From 1.9 version to 2.18 version Closes #31471
strk
added a commit
that referenced
this issue
Aug 29, 2019
From 1.9 version to 2.18 version Closes #31471
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The DBManager TopoViewer plugin uses templates to style layers added to the canvas.
I noticed that the color of symbols, found in the
qml
file, are not honoured, and rather QGIS assigns a different color to nodes everytime a new TopoViewer run is executed.This is a snippet from
python/plugins/db_manager/db_plugins/postgis/plugins/qgis_topoview/templates/node.qml
:Shouldn't the point always be
red="196" blue="176" and green="201"
? Why is it not ? Is this an incompatibility of theqml
format ?NOTE: the file outer node has parameter
qgis version="1.9.0-Master"
The text was updated successfully, but these errors were encountered: