| Numéro d’ID de bogue |
BUG-000115331 |
| Envoi | July 13, 2018 |
| Dernière modification | June 5, 2024 |
| S’applique à | ArcGIS API for JavaScript |
| Version trouvée | 4.8 |
| Système d’exploitation | Windows OS |
| Version du système d’exploitation | 10.0 64 Bit |
| Statut | Will Not Be Addressed
L’équipe de développement a examiné le problème ou la demande et a décidé qu’ils ne seraient pas traités. Pour d’autres explications, reportez-vous à la section Informations supplémentaires correspondant au problème.
|
Informations supplémentaires
This appears to be app specific.
2D and 3D handle resolving the layerView slightly differently. The app appears to work for 2D because the layerView is resolved before the StreamLayer is connected. In the `whenLayerView` block, the `connectionStatus` is initially disconnected. The watcher later fires when the status changes to `connected`. For 3D, this isn't the case so the watcher never fires. This means that the `processConnect` function is never invoked.
The application shouldn't assume that the initial state of the `connectionStatus` is `disconnected`. In the `mapView.whenLayerView(layerView)` block you first need to check what the `connectionStatus` is currently set to, e.g.:
mapView.whenLayerView(streamLayer).then(function(layerView) {
streamLayerView = layerView;
if (layerView.connectionStatus === "connected") {
processConnect();
}
layerView.watch("connectionStatus", function(value) { ... }
If you call `streamLayerView.disconnect()`, the watcher event does get fired.
Étapes pour reproduire
ID de bogue: BUG-000115331
Logiciel:
- ArcGIS API for JavaScript