-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Screen overlay #9864
Screen overlay #9864
Conversation
Thank you so much for the pull request @krupkad! I noticed this is your first pull request and I wanted to say welcome to the Cesium community! The Pull Request Guidelines is a handy reference for making sure your PR gets accepted quickly, so make sure to skim that.
Reviewers, don't forget to make sure that:
|
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.
Source/DataSources/KmlDataSource.js
Outdated
@@ -3333,6 +3514,7 @@ function load(dataSource, entityCollection, data, options) { | |||
* @property {Boolean} [clampToGround=false] true if we want the geometry features (Polygons, LineStrings and LinearRings) clamped to the ground. | |||
* @property {Ellipsoid} [ellipsoid=Ellipsoid.WGS84] The global ellipsoid used for geographical calculations. | |||
* @property {Credit|String} [credit] A credit for the data source, which is displayed on the canvas. | |||
* @property {String} [screenOverlayContainer] A container for ScreenOverlay images. Note: this container is not managed, the caller is responsible for styling and removing unused overlay images. |
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.
Is String
the right type?
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.
seems to be what other docs use for "pass in an element" options
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 ok I see how getElement.js
will accept a string or an element
@mramato I added the |
Awesome, I thought we added something like that but wasn't completely sure. |
Can we update the |
Do you think we should add a container for screen overlays that the |
The web version doesn't have an API (and I'm not even sure it supports screen overlays). The desktop version has no customization either for similar reasons. |
Right, I was thinking the viewer could create an element and Just a thought. If we decide not to do this we might want to show a one time warning if the KML has a screen overlay and the user did not supply a screen overlay container. |
I think that too closely couples everything together. |
eh, maybe. I just thought it might make it easier for folks and make the default functionality more similar to google earth. |
enabled screen overlays in both apps by passing the main container - seems to be working (though the overlay is under the toolbar in sandcastle) |
Nope, looks good to me |
Fixes #9862.
This provides an MVP of KML
ScreenOverlay
support.KMLDataSource.load