You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: The Labeling pane says "Each class labels…" when only one class is visible #993
I searched the existing issues and did not find a duplicate.
This is a bug report, not a usage question (questions belong in Discussions).
What happened?
In the Labeling pane's Content tab, the note under SQL Query, "Each class labels the features its own clause matches, so a feature can get a label from more than one.", shows whenever the layer has any class besides Default, even when that class is hidden. Then only one class labels the layer, so the note is about overlaps that cannot happen. The condition checks for extra classes (!labels.classes.is_empty() in crates/ui-egui/src/labelpane.rs), not for visible ones. CodeRabbit raised it on #967 after the push, and #967 had already been merged.
Steps to reproduce
Open the sample project, select Cities, and open the Labeling pane.
Tick "Label features in this layer".
Add a class with New, then untick Visible for it.
Choose Default again and look under SQL Query in the Content tab.
Expected behavior
The note shows only when more than one class is visible (Default included), as the classes the map draws: labels.in_order() filtered by visible.
Activity
choupeanut commentedon Oct 27, 2026
Update: #994 now implements this fix, so I'm withdrawing my claim to avoid duplicating the existing pull request.
fix(labels): the class rule note only with more than one visible class (