Latest Contributions by JoelBennett

Ok, I see.  Unfortunately, the API has no such flag.  Attached is every use of "console" in the API, and you can see it is quite often used unconditionally.  Perhaps the best alternative is to override the console object's functions in a manner as mentioned by Andrew. ... View more

You can use the filtering tools in your Developer Tools console to hide any unwanted messages, as described here and here.  For example, I prefer not to be inundated with error messages about missing tiles, so I usually have the filter: -blankTile=false -esri.views.2d.layers.TileLayerView2D In your case, perhaps you could have: -identity-manager:user-aborted ... View more

In the Add a Legend to LayerList sample, you can add an opacity slider by changing the contents of the script tag beginning on line 32 to the following: require(["esri/WebMap", "esri/views/MapView", "esri/widgets/LayerList", "esri/widgets/Slider"], ( WebMap, MapView, LayerList, Slider ) => { const map = new WebMap({ portalItem: { id: "d5dda743788a4b0688fe48f43ae7beb9" } }); // Add the map to a MapView const view = new MapView({ container: "viewDiv", map: map }); async function defineActions(event) { const item = event.item; await item.layer.when(); if (item.title === "Census Tracts") { const slider = new Slider({ min: 0, max: 1, precision: 2, values: [1], visibleElements: { labels: true, rangeLabels: true } }); item.panel = { content: ["legend",slider], open: true, className: "esri-icon-sliders-horizontal", title: "Layer Info" }; slider.on("thumb-drag", (event) => { const { value } = event; item.layer.opacity = value; }); } } // Add a legend instance to the panel of a // ListItem in a LayerList instance const layerList = new LayerList({ view: view, listItemCreatedFunction: defineActions }); view.ui.add(layerList, "top-right"); });   ... View more

Without knowing the details of the workflow, it's impossible for me to say.  What is plainly evident, though, is that your custom workflow is using the client-side projection engine, whether explicitly or behind the scenes.  Perhaps it is because the service is returning results in a different coordinate system than the map, thus making projection necessary. Whatever the case, it has a problem with the first search because it hasn't loaded yet.  It seems to be that by the time the second search is attempted, the projection module has fully loaded, and therefore works after that.  The solution is for you to load it yourself prior to any searching taking place.  Perhaps the best way to do that would be to load it before instantiating your Map control, when your application is starting up: require(["esri/map", "esri/geometry/projection", "other/modules"], function(Map, projectionEngine, otherModules) { projectionEngine.load().then(function() { var map = new Map({ //etc }); }); });   ... View more

This error indicates the client-side projection engine is being used before it's fully loaded.  Unlike other modules which you can immediately use after bringing them in via require, define, or declare, the projection engine must be explicitly loaded as well.  Loading this module is asynchronous, so is not immediately available upon calling load.  You must wait until the promise returned by the load function resolves before it can be used. At a minimum, you would need something like this: require(["esri/geometry/projection"], function(projectionEngine) { projectionEngine.load().then(function() { //do geocoding logic }); });   However, it would probably be better to move the importing and loading of this module into your application startup code. ... View more

If your goal is simply to display a CSV file specified from a file input, a much simpler process is possible that never even has to leave the client. You can see this in the sandbox for the sample by replacing the contents of the script tag on line 37 with the following: require([ "esri/Map", "esri/views/MapView", "esri/widgets/Expand", "esri/layers/CSVLayer" ], (Map, MapView, Expand, CSVLayer) => { document .getElementById("uploadForm") .addEventListener("change", (event) => { var reader = new FileReader(); reader.addEventListener("load", function (evt) { var blob = new Blob([evt.target.result], {type:"text/plain"}); var layer = new CSVLayer({url:URL.createObjectURL(blob)}); map.add(layer); expand.collapse(); }); reader.readAsText(event.target.files[0]); }); const map = new Map({ basemap: "dark-gray-vector" }); const view = new MapView({ center: [-41.647, 36.41], zoom: 2, map: map, container: "viewDiv", popup: { defaultPopupTemplateEnabled: true } }); const fileForm = document.getElementById("mainWindow"); const expand = new Expand({ expandIcon: "upload", view: view, content: fileForm }); view.ui.add(expand, "top-right"); });   It loads the sample CSV you provided just fine: ... View more

It's possible you may have shortened your description for simplicity, but disabling the gamepad according to the documentation is shown here under the description of the navigation property. If you've done that and it still doesn't solve your problem, you may have to resort to overwriting the _forEachGamepad function so it doesn't cause the problem.  To do so, you'd need something like this prior to creating your MapView: require(["esri/views/input/gamepad/GamepadSource"], function(g) { g.GamepadSource.prototype._forEachGamepad = function(m) { console.warn("Prevented gamepad access..."); }; });   ... View more

The issue appears to be that just because the visible property changes to true, it doesn't mean the content has yet been added to the popup, and therefore queryable through the DOM. Since the popup doesn't have the equivalent of a "content-ready" event, we have to be a little more creative. I recommend something like the following:   new MutationObserver(function() { if (popup.visible) { var button = document.querySelector("myButtonSelector"); if ((button) && (button.dataset.addedclick != "true")) { button.dataset.addedclick = "true"; //flag to indicate we've set the handler, so action doesn't get repeated unnecessarily button.onclick = function() { //do something }; } } }).observe(popup.container, {childList:true,subtree:true});   ... View more

Very good; thank you also for taking the time to explain. ... View more

A lot has changed in those releases, including the removal of dojo as part of the API in 4.20.  I don't remember the technical specifics of what transpired, but I ended up making my own custom replacement for the text module.  It's called text.js, and I placed it within the root of my own package.  The implementation is very simple: define([], function() { return { load: function(id, require, callback) { var url = require.toUrl(id); var prop = "url:" + url; var cacheVal = require.cache[prop]; if (typeof cacheVal == "string") callback(cacheVal); else { fetch(require.toUrl(id), {credentials:"include"}).then(function(response) { response.text().then(function(text) { require.cache[prop] = text; callback(text); }); }); } } }; });   So then, if you put this text.js file directly in the directory represented by "cuwcd", your function call would change to: require(["cuwcd/text!cuwcd/widgets/Header/header.hbs"], function(hbs) { //etc });   ... View more