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

Rule based symbology sorting with all fields in legend when only linked maps is ticked #60383

Open
2 tasks done
swood44 opened this issue Jan 31, 2025 · 1 comment · May be fixed by #60536
Open
2 tasks done

Rule based symbology sorting with all fields in legend when only linked maps is ticked #60383

swood44 opened this issue Jan 31, 2025 · 1 comment · May be fixed by #60536
Assignees
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Print Layouts Related to QGIS Print Layouts, Atlas or Reporting frameworks Symbology Related to vector layer symbology or renderers

Comments

@swood44
Copy link

swood44 commented Jan 31, 2025

What is the bug or the crash?

The issue occurs when using rule based symbologies with a greater number of classes then displayed on a map. When you go to the legend in a print layout, and tick 'Only show items in linked maps' the legend will hide any rule based classes that are not shown in the map. However, when trying to rearrange the order of any remaining legend items you must click the arrows extra times before they reorganise, I believe that this is due to them rearranging based on all labels, rather than only the labels shown in the map.

Steps to reproduce the issue

Open a the project 'Broken Legend'
Open Print Layout 'map1'
In the 'Item Properties' for the legend try moving SC down to the bottom. It will take several clicks of the down arrow.
If you untick the 'Only show inside linked maps' button you will see that it has reordered the whole list of possible symbologies.

BrokenLegend.zip

Versions

QGIS version
3.40.3-Bratislava
QGIS code revision
2a274ab

Libraries
Qt version
5.15.13
Python version
3.12.8
GDAL/OGR version
3.10.1
PROJ version
9.5.1
EPSG Registry database version
v11.022 (2024-11-05)
GEOS version
3.13.0-CAPI-1.19.0
SQLite version
3.46.1
PDAL version
2.8.3
PostgreSQL client version
unknown
SpatiaLite version
5.1.0
QWT version
6.3.0
QScintilla2 version
2.14.1
OS version
Windows 11 Version 2009

Active Python plugins
db_manager
0.1.20
grassprovider
2.12.99
MetaSearch
0.3.6
processing
2.12.99

Supported QGIS version

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

New profile

Additional context

No response

@swood44 swood44 added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label Jan 31, 2025
@agiudiceandrea agiudiceandrea added Symbology Related to vector layer symbology or renderers Print Layouts Related to QGIS Print Layouts, Atlas or Reporting frameworks labels Feb 4, 2025
@Djedouas Djedouas self-assigned this Feb 10, 2025
Djedouas added a commit to Djedouas/QGIS that referenced this issue Feb 10, 2025
…ltered

Fixes qgis#60383.

In a layout, when moving a legend node on a filtered legend, the
computed offset was wrong if some nodes were hidden between the node to
move and its destination.

The offset is now computed with the next/previous visible index.
@Djedouas
Copy link
Member

Thanks for the sample project and the description, it helped to understand :)

Djedouas added a commit to Djedouas/QGIS that referenced this issue Feb 12, 2025
…ltered

Fixes qgis#60383.

In a layout, when moving a legend node on a filtered legend, the
computed offset was wrong if some nodes were hidden between the node to
move and its destination.

The offset is now computed with the next/previous visible index.
troopa81 pushed a commit to troopa81/QGIS that referenced this issue Feb 13, 2025
…ltered

Fixes qgis#60383.

In a layout, when moving a legend node on a filtered legend, the
computed offset was wrong if some nodes were hidden between the node to
move and its destination.

The offset is now computed with the next/previous visible index.
Djedouas added a commit to Djedouas/QGIS that referenced this issue Feb 21, 2025
…ltered

Fixes qgis#60383.

In a layout, when moving a legend node on a filtered legend, the
computed offset was wrong if some nodes were hidden between the node to
move and its destination.

The offset is now computed with the next/previous visible index.
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! Print Layouts Related to QGIS Print Layouts, Atlas or Reporting frameworks Symbology Related to vector layer symbology or renderers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants