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.
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
Fix scale bar text being cut #1716
Fix scale bar text being cut #1716
Changes from 10 commits
e88df19
131b56d
ef46663
536f91a
91e3194
5d0fbb7
f89d051
19c5c7d
9a457fb
a725d18
ef51c61
64cdac4
a65bbc6
512acd5
f97571a
b964151
d0adea0
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
should we create similar activity on iOS for parity and making sure that our scalebar customizations are aligned? @mapbox/maps-ios
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.
is it ok that we check
x
here but operate withsafeX
below?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.
You're right. It's better to use
safeX
.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.
and also for better readability I'd use
if (x < trokePaint.strokeWidth / 2)
similar to L316There 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.
Hmmm I personally think that:
it's a bit obscure.
I need to think more to figure out why we're comparing a position (
x
orsafeX
) with a width (strokeWidth
). Somehow, to me, mine reads easier: to positionsafeX
I remove a width and then check if it goes beyond the left minimum position (0
).But happy to change it to your proposal if others also prefer it.