Bug report #13318
Data-defined symbology seriously broken
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Severe/Regression | ||
| Assignee: |  Nyall Dawson | ||
| Category: | Symbology | ||
| Affected QGIS version: | master | Regression?: | No |
| Operating System: | Easy fix?: | No | |
| Pull Request or Patch supplied: | No | Resolution: | |
| Crashes QGIS or corrupts data: | No | Copied to github as #: | 21374 |
Description
In current master (as of 03916d5 - Sep. 3) there is something seriously broken in data-defined symbology.
Actually I don't know if it is the data-defined symbology or something bad on the provider. Anyway, please have a look at the attached project. In this project I use data-defined coloring and data-defined stroke-width.
If you navigate or reload, you can see that colors and line-widths randomly change - as if there suddenly would be different attributes attached to the same geometries.
Something is seriously broken.
I know that bcaee65 from 15 days ago was still ok.
I am trying to narrow down the issue with different commits.
Associated revisions
Fix data defined rendering for rulebased/inverted polygon renderers
fix #13318
History
#1
Updated by Andreas Neumann over 9 years ago
Here is the link to the project - file was too big to attach it to this bug report.
#2
Updated by Andreas Neumann over 9 years ago
- Assignee set to Nyall Dawson
So far - my git bisect indicates that this bug was introduced with the new expression contexts (commits from August 22)
#3
Updated by Nyall Dawson over 9 years ago
- Status changed from Open to Closed
Fixed in changeset bef84dc67650cd89dc0bad95596e3caeb7de0383.