There were a few areas in Source where a function was assumed to be executed synchronously when a function was resolved. Native Promises however, by spec, will resolve at the end of a frame. There were also some strange handling of promise rejection in imagery providers that I cleaned up a bit in order to make them testable.
- In LabelCollection and EntityCluster, order of execution adjustment where made.
- Added TextureAtlas.addImageSync to support the order of execution fix in LabelCollection
- ArcGisMapServerImageryProvider.readyPromise will not reject if there is a failure unless the request cannot be retried.
- SingleTileImageryProvider.readyPromise will not reject if there is a failure unless the request cannot be retried.
The majority of the changes lie in the Specs, where unresolved promises weren’t being awaited before finishing executions, and where resolved promises are assumed to be synchronous all over the place and needed a good amount of fixes. Another issue which came up was calling Promise.reject in the body of a spec can cause node to halt execution when running via the command line.
This change enabled CZML and the Entity API to load 3D Tiles tilesets.
Since `Cesium3DTileset` has dozens of options, I only exposed
uri/show/maximumScreenSpaceError to start. We also use the entity
position/orientation (if specified) to compute the tileset.modelMatrix
allowing for moving tilesets that can be tracked with the camera.
Details:
1. New Sandcastle example, `CZML 3D Tiles.html`
2. New class, `Cesium3DTilesetGraphics` for representing a tileset via
the Entity API.
3. New class, `Cesium3DTilesetVisualizer` for creating/managing the
primitives.
4. Add `Entity.tileset` which is an instance of `Cesium3DTilesetGraphics`
5. Specs for everything
jjspace
Gabby Getz
Sanjeet Suhag
Matthew Amato