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(mapbox) leave additional views intact #6329
Conversation
@@ -14,7 +14,7 @@ Use deck.gl layers as custom Mapbox layers, enabling seamless interleaving of Ma | |||
|
|||
### Limitations | |||
|
|||
* deck.gl's multi-view system cannot be used. | |||
* deck.gl's multi-view system only supports one MapView (e.g. minimaps are not supported). |
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.
Technically speaking you can have multiple MapView
s, the limitation is that you will always have a MapView that fills the entire canvas (what Mapbox draws into).
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.
Ah, is that why minimap views can't use mapbox? I'd like to explain the limitation better in the overview in case its useful to someone hacking around it.
e16ca37
to
6671fb9
Compare
Background
The deck/mapbox interleaved rendering needs to reproject the viewport to match mapbox when an external deck object is provided. Currently the extension assumes the first View is a
MapView
and deletes any other viewports, however deletion is unnecessary and not expected if provided multiple views (e.g. a minimap or info viz overlay).Result After Fix
TextLayer on OrthographicView renders on top of interleaved MapView.
Change List
Related to interleaved mapbox rendering:
viewId
provided - same behavior as todayviewId
provided and found - replace specified viewportviewId
provided and not found - do nothing