Skip to content
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

layer fails to render when rule-based symbology make use of $atlasfeatureid #18051

Closed
qgib opened this issue Jan 30, 2014 · 3 comments
Closed
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Expressions Related to the QGIS expression engine or specific expression functions

Comments

@qgib
Copy link
Contributor

qgib commented Jan 30, 2014

Author Name: Mathieu Pellerin - nIRV (Mathieu Pellerin - nIRV)
Original Redmine Issue: 9459
Affected QGIS version: master
Redmine category:expressions
Assignee: Nathan Woodrow


In an atlas-defined project, a layer that has a rule-based symbology that relies on the $atlasfeatureid will not render upon project loading. The user will have to enter the layer's property window, and click on apply / ok for the layer to start rendering.

A basic scenario that leads to this problem is when a user will use a $id = $atlasfeatureid / $id != $atlasfeatureid set of rule to highlight the atlas feature on the map.

It's a bit of an odd one, so I'll let the attached test project showcase the problem.


@qgib
Copy link
Contributor Author

qgib commented Jan 30, 2014

Author Name: Paolo Cavallini (@pcav)


  • fixed_version_id was changed from Version 2.0.0 to Future Release - High Priority

@qgib
Copy link
Contributor Author

qgib commented Feb 8, 2014

Author Name: Nyall Dawson (@nyalldawson)


Think this should be a blocker, since it's a new feature which isn't working as expected.

I had a go at fixing it by making sure that $atlasfeatureid is set to 0 when an atlas based composition is first loaded, but this fix didn't work since the map has already been rendered by the time the composition is loaded.

I think this global variable needs to be set to 0 when a project is loaded but before any map is rendered.


  • priority_id was changed from Normal to Severe/Regression

@qgib
Copy link
Contributor Author

qgib commented Feb 11, 2014

Author Name: Martin Dobias (@wonder-sk)


Fixed in changeset "684dd890a3359a2fb189b289b0bb65a42a9f4105".


  • status_id was changed from Open to Closed

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Expressions Related to the QGIS expression engine or specific expression functions labels May 24, 2019
@qgib qgib added this to the Future Release - High Priority milestone May 24, 2019
@qgib qgib closed this as completed May 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Expressions Related to the QGIS expression engine or specific expression functions
Projects
None yet
Development

No branches or pull requests

1 participant