Latest Contributions by FranklinAlexander

Just wandering if anyone else is experiencing performance issues with EB online lately. After about the first hour or so, EB starts getting extremely slow and I start experiencing minor, but annoying bugs. Most common is when trying to make styling changes to a panel, widget, etc. (ex. border radius) not being applied to the panel, or at least it doesn't appear they are being applied. I am running EB in Chrome, so not sure if this is a browser issue and I don't want to run EB in another browser unless I have no choice. Closing the browser and reloading EB doesn't seem to help, so I am having to restart my computer to get EB to run correctly. Could it be a cache issue? My browser cache (image and files) was up to 253 MB which I did clear, but that doesn't seem high enough to me to be causing issues since my PC has plenty of available memory. Unless Esri stores the cache for the working projects at ArcGIS online and I could see that being an issue. Just curious if anyone has any thoughts on this. ... View more

I am working on a custom widget for an EB Developer application and the on 'click' event won't fire when in mobile layout, but fires as expected in Desktop and Table layout. Each layout does have it's own map and I do have access to the map view in each case, so I don't think that is the issue. Also, nothing is blocking the map in mobile layout (verified in the Page outline) and I have popups enabled for the map.  jimuMapView.view.whenLayerView(cLayer).then((layerView) => { let highlight const mapDiv = document.getElementById("jimu-widget-a11y-widget_47") console.log("jimu map view ", jimuMapView) //this is defined jimuMapView.view.on("click", function(evt) { console.log("click zoom level ", jimuMapView.view.zoom) let screenPoint = { x: evt.x, y: evt.y } jimuMapView.view.hitTest(screenPoint, {include[cLayer]}) .then(function(resp) { console.log("Hello!") const graphHits = resp.results?.filter( (hitResult) => hitResult.type === "graphic" ); if(graphHits?.length > 0) { const county = graphHits[0].graphic.attributes.COUNTY if(county && currCounty !== county) { if (jimuMapView.view.zoom >= 6 && jimuMapView.view.zoom < 8.5) { highlight && highlight.remove(); highlight = layerView.highlight(graphHits[0].graphic); hoverCty.current = county hoverGraph.current = graphHits[0].graphic showLabel(county, screenPoint, mapDiv) } else { if(mapDiv.hasChildNodes() && mapDiv.childNodes.length > 1) { mapDiv.removeChild(mapDiv.childNodes[1]) } } hoverCty.current = county } } else { if(mapDiv.hasChildNodes() && mapDiv.childNodes.length > 1) { mapDiv.removeChild(mapDiv.childNodes[1]) hoverCty.current = "" } highlight && highlight.remove(); } }) }) })   ... View more

I am working on a custom Query widget for an Experience Builder application that queries a REST service and displays the results on the map. The map currently contains a county boundaries layer that I would like to use to display the results because I need the geometry from the layer. My challenge is that I need to add 8 new fields to the county boundaries at runtime that contain response data from the query. We currently have a WAB app with a custom widget that does this very thing, but this was more straight forward with the JS 3x api. The 4x api has so many different types feature layers and views with varying degrees of usability, that trying to figure out the best workflow and what layer type to use is making my head explode! It would be nice if I could just create a layer view to the county boundaries, then join a json object containing the new fields with the response data. This would be fast and keep everything client side, but not sure if this is possible. Just looking for general advice right now on the best workflow here so not providing code just yet. ... View more

I am working on a WAB online app that contains a Smart Editor widget and I need to replace the widget because it has bugs. When I open the 'Choose Widget' dialog, there is no Smart Widget. Has this widget been removed and is not supported any more, or am I missing something?  ... View more

In the latest Experience Builder update, Esri touted the addition of the 'Use Current Location' option for the Near Me widget. I knew that this was in the works, but had envisioned that this would become an option (button) in the actual widget, not another action item to be configured from another widget. I don't really see this as an improvement since I could do the same thing with the Search widget, but the using the Search widget is actually better because I can at least add it in such a way that it looks like its part of the Near Me widget. The only way a user is going to know that they can click the 'My Location' button in the map to find features near whatever layer the Near Me widget is connected to is if you tell them.   Don't really understand why Esri can't just make this a part of the widget. Here is one of my first customizations in WAB before I even knew what I was doing: The version in the above image makes so much more sense to me because it's straight forward and doesn't leave the end user guessing. Will probably go back to using the Search widget because it gives the user a choice between searching from a typed address or their location. And I almost forget, the maps 'My Location' tool zooms all the way in to the users location, then has to zoom out to the extent of the Near Me results. The zoom action for the map's Location tool needs to be turned off when it is the trigger for the Near Me widget.   ... View more