Keep FOV search radius on hiDPI screen consistent from user perspective #3985
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I briefly looked into the issue #3733 because the issue of selecting the wrong star/ not selecting any stars even clicked near a star somewhat are becoming more problematic when some sky regions can have stars densely packed together with future star catalogs with Gaia. Although this PR does not fix anything, but a minor logical improvement until someone takes a deep dive into the issue after the new star catalogs are done because things can still be changed around.
I've found that the FOV to search around are penalized for user with a scaled high DPI screen by the display scaling factor. So hiDPI screen users are expected to click closer to a star in order for it to be searched. Now the FOV to search should be independent of display scaling (N pixels from user perspective around the mouse click will be searched)
Fixes # (issue)
None
Screenshots (if appropriate):
Type of change
How Has This Been Tested?
Test Configuration:
Checklist: