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 style panel and Layer panel do not show same visibility settings for layer style #49998

Closed
1 of 2 tasks
sherbie182 opened this issue Aug 29, 2022 · 5 comments
Closed
1 of 2 tasks
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Feedback Waiting on the submitter for answers stale Uh oh! Seems this work is abandoned, and the PR is about to close.

Comments

@sherbie182
Copy link

What is the bug or the crash?

Layer style panel and Layer panel do not show same visibility settings. Layer style panel seems to have dominate behaviour - ie. the layer symbols as shown on the map panel match those as selected on the layer style panel.

image

In the example screen shown, note the six styles shown for the TREE DENSITY layer. In the Layer panel (left), only the shading styles are selected. In contradiction, the shading styles plus one fill pattern style are selected in the Layer style panel. The map panel shows the 4 selected styles as defined by the Layer style panel.

Steps to reproduce the issue

See bug description. I am unsure whether specific steps lead to this happening. I believe the behaviour may have existed on 3.19 before I updated to 3.26.2 but can't be 100% sure.

Versions

QGIS version
3.26.2-Buenos Aires
QGIS code revision
feec3d3
Qt version
5.15.3
Python version
3.9.5
GDAL/OGR version
3.5.1
PROJ version
9.0.1
EPSG Registry database version
v10.064 (2022-05-19)
GEOS version
3.10.3-CAPI-1.16.1
SQLite version
3.38.1
PDAL version
2.4.2
PostgreSQL client version
unknown
SpatiaLite version
5.0.1
QWT version
6.1.6
QScintilla2 version
2.13.1
OS version
Windows 10 Version 2009

Active Python plugins
linz-data-importer
2.2.3
MagneticDeclination
2.3.1
pointsamplingtool
0.5.3
profiletool
4.2.2
qgis-maptiler-plugin
2.0.0
qgis_resource_sharing
0.16.0
QuickOSM
2.0.1
quick_map_services
0.19.28
trail_elevation_stats
0.2
db_manager
0.1.20
grassprovider
2.12.99
MetaSearch
0.3.6
processing
2.12.99
sagaprovider
2.12.99

Supported QGIS version

  • I'm running a supported QGIS version according to the roadmap.

New profile

  • I tried with a new QGIS profile

Additional context

No response

@sherbie182 sherbie182 added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label Aug 29, 2022
@elpaso
Copy link
Contributor

elpaso commented Sep 16, 2022

Cannot reproduce on current master. Can you attach a sample project and data where the issue can be reproduced?
Also, please try with a new profile.

@elpaso elpaso added the Feedback Waiting on the submitter for answers label Sep 16, 2022
@github-actions
Copy link

github-actions bot commented Oct 1, 2022

The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale".
If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue.
In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue.
If there is no further activity on this issue, it will be closed in a week.

@github-actions github-actions bot added the stale Uh oh! Seems this work is abandoned, and the PR is about to close. label Oct 1, 2022
@sherbie182
Copy link
Author

I'll have to tear this rather large project apart into a smaller file to share with you.

What do you mean by trying with a new profile?

@github-actions github-actions bot removed the stale Uh oh! Seems this work is abandoned, and the PR is about to close. label Oct 10, 2022
@github-actions
Copy link

The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale".
If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue.
In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue.
If there is no further activity on this issue, it will be closed in a week.

@github-actions github-actions bot added the stale Uh oh! Seems this work is abandoned, and the PR is about to close. label Oct 24, 2022
@github-actions
Copy link

While we hate to see this happen, this issue has been automatically closed because it has not had any activity in the last 42 days despite being marked as feedback. If this issue should be reconsidered, please follow the guidelines in the previous comment and reopen this issue.
Or, if you have any further questions, there are also further support channels that can help you.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 22, 2022
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! Feedback Waiting on the submitter for answers stale Uh oh! Seems this work is abandoned, and the PR is about to close.
Projects
None yet
Development

No branches or pull requests

2 participants