Karim Naaji
Karim Naaji
Fixes https://github.com/mapbox/gl-js-team/issues/479 This PR adds support for `cameraForBounds` on globe and updates the method used by `cameraForBounds` to account fully for 3d perspective. A demo of the prototype to help...
When globe is enabled, we use a mock DEM data source cache as a placeholder to leverage the draping architecture (in order to capture tiled texture to render as raster)....
**mapbox-gl-js version**: 2.0.0 Camera functions `flyTo` and `easeTo` are not taking terrain elevation properly into account leading to bumpy and jittery camera movement. The approach used in our camera system...
This issue was reproducible on a 1x pixel density screen pixel on a dark style (mapbox://styles/mapbox/dark-v10). Some pixels may be rendered incorrectly as white, as they fall on and off...
From @stevage in https://github.com/mapbox/mapbox-gl-js/issues/10784#issuecomment-1050370220: >After setting the globe projection, when I add a GeoJSON source, I weirdly get: > >>Error: terrain: terrain is missing required property "source" > >Adding terrain...
Supersedes PR https://github.com/tangrams/tangram-es/pull/1812 (thanks to @tehKaiN for the initial work on this): - Add platform layer for Windows platform. - Add initial AppVeyor configuration (https://ci.appveyor.com/project/karimnaaji/tangram-es -- currently building my own...
Inlay blend mode is incompatible with our text and point styles, the reason being that the depth of text and icons is not in _world space_ but in _screen space_...
It seems that the signature of fons__tt_init weren't the same in the stb true type and free type. Just fixed that by adding a lazy FONScontext\* parameter.
**Current behavior** Line geometry between two points on globe does not use use shortest distance and there can be non-intuitive behavior around the poles where the points are always projected...