forked from CesiumGS/cesium
-
Notifications
You must be signed in to change notification settings - Fork 21
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
Upgrade to Cesium 1.15 #3
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…into boxOutlineGeometry-cleanup
As discussed in CesiumGS#3083, these primitives are no longer needed and add confusion to the public API. I also replaced usage of them in any tests with the equivalent G&A code.
…the-old Deprecate EllipsoidPrimitive, RectanglePrimitive, and Polygon
…XT_frag_depth aren't supported.
BoxOutlineGeometry and BoxGeometry Cleanup
Run `ant sortRequires` Update package.json to latest modules.
…ires Minor cleanup
Geocoder flies to rectangle crossing IDL
Previously, when the clock had a multiplier larger than the largest shuttle ring tick mark, the dial marker would end up going offscreen making it impossible to adjust the multiplier through the UI. Ancient code tried to account for this by expanding the list of valid ticks to include the new multiplier. Unfortunately, that approach isn't ideal because it would change user settings out from under them. Instead, this approach simply sets the dial to it's max value when the muliplier is larger and the first click to slow things down will snap to the largest actual tick. Fixes CesiumGS#1072
Initial WebStorm project
glTF 1.0 Changes
…eViewRectangle Replace deprecated viewRectangle in Sandcastle examples
…-build Don't build or include Cesium Viewer as part of release.
test fixes for TileMapServiceImageryProvider
Fix problems with joinUrls and absolute URLs.
It turns out that there are a bunch of places in our code where we use `when.defer()` and return the deferred instance instead of its `promise` property. This works in most cases because when's deferred promises are thenable, however they don't have all of when's API, like `always`. This change makes sure we correctly return `deferred.promise` everywhere. It's probably a quirk of the version of when we are using that defers aren't always-able and always isn't part of the A+ spec, so there's no reason to add additional tests for these.
…cated Ignore the deprecated Scene version of HeadingPitchRange
…-always Fix when.defer() usage
1.15 release Conflicts: Source/Workers/cesiumWorkerBootstrapper.js gulpfile.js package.json
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.