-
Notifications
You must be signed in to change notification settings - Fork 315
Simplification of the loading process for rasterized tiles and mesh tiles #2609
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
base: master
Are you sure you want to change the base?
Conversation
489581c to
afdfc01
Compare
|
Rebased |
|
I’ve come up with a possible way to simplify this — what do you think of these changes? |
afdfc01 to
6f64fdf
Compare
2cec783 to
15dfa04
Compare
|
c7b4635 to
4bd5c32
Compare
|
|
e9aab85 to
3d3be67
Compare
592d39a to
4bdf282
Compare
e175c90 to
ab558ea
Compare
eecc503 to
4c86123
Compare
4c86123 to
3d5de39
Compare
a55f702 to
5235375
Compare
5235375 to
7a3ea9a
Compare
Description
This PR proposes a possible simplification of the loading process for rasterized tiles and mesh tiles.
Summary of changes
TileMeshinstances are now created directly inTiledGeometryLayer, without using commands or providers.TileMesh.pendingSubdivisionhas been removed.TiledGeometryLayer#hasEnoughTexturesToSubdividehas been removed.updateLayeredMaterialNodeImageryandupdateLayeredMaterialNodeElevationhave been merged into a single lightweight method.TileProviderhas been deleted.RasterTile#load.