-
-
Notifications
You must be signed in to change notification settings - Fork 838
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
Tweak screen intersect callback #3059
Conversation
- avoid text intersection
Great PR! Please pay attention to the following items before merging: Files matching
This is an automatically generated QA checklist based on modified files. |
Upward curves in bottom right edge are still not OK. |
In the following screenshot, the Similarly in the following screenshot, the |
-also remove second approach
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not complete solution, but acceptable
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, at least the clipping is not as severe as it used to be, although text placement and orientation still leaves a lot to be desired.
Hello @gzotti! The enhancement or feature has been merged into source code and you may test it via building Stellarium from source code or wait the weekly development snapshot... |
Hello @gzotti! The fix has been merged into source code and you may test it via building Stellarium from source code or wait the weekly development snapshot... |
Hello @gzotti! Please check the fresh version (development snapshot) of Stellarium: |
Hello @gzotti! Please check the latest stable version of Stellarium: |
This is a small correction to the screen intersect callback to label SkyLines. It shall avoid loss of a few characters which are shifted out of the actual screen area by shallow angles.
There are two possible ways. Shifting the text, or changing the placement position. Currently it seems the first is enough, but I have left the other way commented out.
Please TEST!
Description
Fixes #2955 (issue)
Screenshots (if appropriate):
Type of change
How Has This Been Tested?
Test Configuration:
Checklist: