Fix those occlusion problems #168
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jaysondc
approved these changes
Sep 4, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Dear developer:
Hello! I am the creator of issue #167, and I have fixed those aforementioned occlusion problems. I would genuinely appreciate it if you could kindly revise my code and leave me some advice. Thank you so much for your precious time!
Here are the screenshots after my changes. And I would also like to say that in the first screenshot, I want to keep the consistency of size among those names, so I make the longer string end with ellipsises, and I still could know the monster's full name on the corresponding summary page:
Thanks again! Blessings on your day! :)