-
Notifications
You must be signed in to change notification settings - Fork 327
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
Features are not picked when in 3D mode #344
Comments
The 2D OL3 interactions are not made available in 3D. OL3
|
Sorry, that was elaborated separately in #345 -I have removed it from the issue description. |
I am not sure what has happened with the description, as the cluster discussion was meant to be only in #346. I have just updated the issue description. |
So, is this something that can be supported in some other way on the application side, or something that could be in the roadmap for ol3-cesium? |
The application can of course set a listener in Cesium and react to pointer move or click. We could also imagine OL3-Cesium doing this automatically. Maybe this could be experimented with the OL3 select interaction. |
Actually, I just checked that the click event is triggered when I click on the 3D map. What really happens is that when the click event came with the 3D map enabled, map.forEachFeatureAtPixel does not return anything. |
So, I have workarounded the events issue replacing the calls to map.forEachFeatureAtPixel with the following function (from both "pointermove" and "click" events):
In a nutshell, this check whether we are in Cesium or OpenLayers rendering mode, and uses scene.pick or map.forEachFeatureAtPixel depending on the case. Could an adapted version of this be of use to ol3-cesium? |
Would be an interesting experimentation for OL3-Cesium. |
Using a Vector/KML layer in OpenLayers 3. When using ol3-cesium in 3D mode this is somewhat working.
However, the map "pointermove" and "click" events are not triggered when placing the mouse over the feature or clicking on it.
The text was updated successfully, but these errors were encountered: