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

Add feature map tool: Make highlight width always bigger than rubberband #59447

Conversation

JuhoErvasti
Copy link
Contributor

There's no issue for this, since this addresses an oversight in #59424. I wasn't sure if one should be created in this case.

The highlight width was hardcoded to 2, which didn't take into account the user having potentially changed the rubberband width. Now the width will always be set as wider than the rubberband.

I also applied the width to polygons for consistency and in case the user has set an opaque rubberband.

@github-actions github-actions bot added this to the 3.42.0 milestone Nov 14, 2024
@JuhoErvasti
Copy link
Contributor Author

JuhoErvasti commented Nov 14, 2024

I wasn't sure if I should change this as well: the color of the highlight is currently set from the Identify tool's settings. This has been the case for point features for probably quite some time so I felt reticent to change it in case someone's using it.

But IMO it'd make more sense to use the rubberband's colors.

Copy link

github-actions bot commented Nov 14, 2024

🪟 Windows builds

Download Windows builds of this PR for testing.
Debug symbols for this build are available here.
(Built from commit 1560d16)

🪟 Windows Qt6 builds

Download Windows Qt6 builds of this PR for testing.
(Built from commit 1560d16)

@nyalldawson nyalldawson merged commit a4dca08 into qgis:master Nov 25, 2024
33 checks passed
@JuhoErvasti JuhoErvasti deleted the 50671_feature_attributes_form_should_have_a_way_to_highlight_feature_on_map branch November 25, 2024 14:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants