Latest Contributions by SebastianKvist

Thank you Robert and Arne. I provide the original example with applied workarounds from you both and some additions. To get it to work in all use cases with v4.8+, I had to do the following (please note the two "workaround"-comments): require([       "esri/views/MapView",       "esri/Map",       "esri/layers/MapImageLayer",        "esri/core/watchUtils"     ], function(       MapView, Map, MapImageLayer, watchUtils     ) {       var mapConfigs = [         {},         {},         {}       ];       /************************************************************        * Create multiple map instances, each with one         * MapImageLayer-instance added to it..        ************************************************************/       var maps = mapConfigs.map(function(mapConfig) {         var map = new Map(mapConfig);         map.add(new MapImageLayer({           url: 'https://sampleserver6.arcgisonline.com/arcgis/rest/services/SampleWorldCities/MapServer'         }));         return map;       });       /************************************************************        * Initialize the View with the first Map        ************************************************************/       var view = new MapView({         map: maps[0],         container: "viewDiv"       });               // Workaround for v4.8+        view.when(function() {           view.goTo(view.extent.clone());        });       document.querySelector(".btns").addEventListener("click", function(         event) {         /************************************************************          * On a button click, change the map of the View          ************************************************************/         var id = event.target.getAttribute("data-id");         if (id) {           var map = maps[id];                      view.map = map;                         // Workaround for v4.8+             watchUtils.whenTrue(view, "ready", function() {                watchUtils.whenTrueOnce(view, "stationary", function() {                  view.goTo(view.extent.clone());                });           });           var nodes = document.querySelectorAll(".btn-switch");           for (var idx = 0; idx < nodes.length; idx++) {             var node = nodes[idx];             var mapIndex = node.getAttribute("data-id");             if (mapIndex === id) {               node.classList.add("active-map");             } else {               node.classList.remove("active-map");             }           }         }       });     });‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ If I go back to 4.7 - i can inactivate the two commented workaround sections and see the mapView loaded both initially and when switching between the different map-objects. Using 4.8 or later, I find that I need the first workaround section to trigger the initial data-fetching for the default map object. The second workaround section is needed for when I swap the map object. Note that it is a nested watcher, it wasn't sufficient with just 'stationary' or 'ready' - but a combination of both.. Its an acceptable workaround, even if the user experience differ somewhat (was a smoother and somewhat faster switch with 4.7). Thanks again! ... View more

Thank you for your answer. Yes, I imagined the possibility of it being a bug - however I noticed we actually recreate some widgets when the map changed, which in fact seem to have triggered this error. The error mentioned above would present itself when I recreated the Print widget, rather than the LayerList widget. Anyways, the key question here was regarding the ability to reuse the MapView instance and then in turn reuse widget instances depending on the same MapView. I feel I have gotten the answer to that. Regards,  Sebastian ... View more

Thanks for your responses. Please get back on this matter when a solution is available. ... View more