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 camera method and address deprecations #3602
base: main
Are you sure you want to change the base?
Fix camera method and address deprecations #3602
Changes from 5 commits
89d57ba
c470fa3
23c237c
1234883
c602be7
5823880
5290700
762c1e7
42e6726
8582e6b
bc011ab
715adf7
67183ff
2f46a22
0aaa177
6c91f71
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.
I've found that I have more consistant results by using
zoom: .zero
. If zoom is set on this camera is seems to effect the positioning.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.
@mfazekas @naftalibeder I'll aim to make a demo this afternoon of why i've highlighted this.. but when moving the camera with setCamera from a centerCoordinates position to setCamera with bounds it seems that zoom is applied to the final position. Adding this
zoom: .zero
looks to fix this problem thou I need to look at why.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.
why do we use coordinatePadding and not camera padding?
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'm not sure about this on remove. Maybe just
mapView?.viewport
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 don't understand the comment exactly -
mapView
doesn't need optional chaining if acquired in thewithMapView
callback. What's the concern?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.
First it should be
map.withMapView { }
we're in remove so we have a RNMBXMapView we're removing from, passed in as argument .Second if mapView of RNMBXMapView is null then what was the satusObserver was attached to? Why do we need to remove?
So I think withMapView is unnecessary in this case. Likely not harmful but you have the check carefully as it could easily keep the camera object alive, until we'll have a mapView. Which doesn't sound right, but probably no leak here.
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 don't have a strong sense of the implications of the callback architecture (
_mapCallbacks.append(callback)
, etc.).We can do
but since
_mapView
is force-unwrapped, I'm not sure if it could be nil when acquired that way. It'd be the only place in the camera module wheremap.mapView
is referenced that way. Do you prefer themap._mapView
syntax?