-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
add support for min/max scale limits #5192
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
Open
mojoaxel
wants to merge
7
commits into
plotly:master
Choose a base branch
from
fllstx:5191-geo-zoom-limit
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+61
−1
Open
Changes from 1 commit
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
a392b74
feat(geo): support min/max scale limits
mojoaxel df23838
refactor: rename min/max scale limits
mojoaxel 388c0b0
chore: use dflt: -1 instad of null
mojoaxel d531576
feat: handle maxscale default in scaleExtent
mojoaxel b0daf38
chore: only r
8000
erender on zoom if scale changes
mojoaxel b46375a
chore: fix typo in min/maxscale attributes
mojoaxel c42cb9d
test: adopt test/plot-schema.json to new plot-schema
mojoaxel File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
chore: use dflt: -1 instad of null
- Loading branch information
commit 388c0b0072f11d4077b246cde1a6f8ebc12e0627
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
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.
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.
Now we need to handle
or
if we decide to use
-1
instead ofnull
which is not anumber
.@alexcjohnson your idea on which one is better?
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.
With e722947 I changed the default to
-1
instead ofnull
. Scales with less than 0 make no sense here so this should be a valid solution.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.
I suppose
-1
as a default is OK if we really need a "no max" value - it's better thannull
which behaves oddly inrelayout
.But I wonder if we can't pick a decent default that's more zoomed in than is generally ever useful. I have occasionally gotten in a situation by accidentally scroll zooming so far in that everything freezes up because the SVG engine is having trouble drawing all the off-screen elements. If we cover 99% of cases and avoid this pitfall I'd say that's a reasonable tradeoff, and avoids making a coded value. Something like
10,000
?Similarly, is there a default we could use for minscale, to avoid zooming the whole map away to a point?
0.1
perhaps?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.
Makes sense!
(I'll have a look tomorrow. It's getting late her in europe 😴)