Latest Contributions by FC_Basson

‎03-13-2024

Hi @AndyGup Yes, the apps with graphic layers work on other PCs. It is only this one that is a headache. - PC make and model >> Proline (desktop) - Operating system and version - Intel Graphics card driver name and version - browser and version >> Chrome 122.0.6261.113 (Official Build) (64-bit)

‎03-13-2024

Hi @mgeorge I've attached the full report.

‎03-12-2024

I have an issue with graphics layers on one of our PCs - graphics layers are not visible at all on a 2D MapView. I can confirm that the graphics are indeed in the graphics layer items, with correct geometries and symbology. This happens with the JS API (4.29) as well as in AGOL webmaps, so the issue is not on the code side. When I switch from 2D MapView to 3D SceneView, using the same Map, the graphics layer is visible in the 3D SceneView. The browser used is WebGL2 enabled, as can be confirmed by visiting https://get.webgl.org/webgl2. The PC uses only an internal Intel Graphics card (no GPU) and has only 8Gb RAM. Could the PC resources be the issue here or are there some other tests I can do ?

‎03-11-2024

Hi @Sage_Wall This is the piece of code that breaks the select: if (item.layer.type == "group") { item.sortable = false; } This check is done directly after the item is received from the create event. I don't want the group layers to be sortable, but the child layers can be sorted, hence the "false" setting of the "sortable" property.

‎03-11-2024

I use plenty of DOM queries, of which many start at document level and they all work. When I isolate the "listItemCreatedFunction" code, the select works. Unfortunately I can't share the larger code base.

‎03-11-2024

After removing all jQuery from my code, I am still experiencing the same issue with JS API 4.29 and CDS 2.6.0.

‎03-06-2024

Thanks, I was actually just reading that blog. But still, with 4.28 all my jQuery was working fine.

‎03-05-2024

I've run into some other issues too, especially with elements with jQuery interaction - events are not working as expected any longer. I've noticed in the DOM that 4.29 creates a new encapsulating element of class "interaction-container" - what exactly does this container do?

‎03-03-2024

I did some more inspection and simplified my panel content to include only the select, similar to you codepen example (which I see you've updated to enable the layer drag), but still the issue persists. There is definitely some issue with the select click events. In the Event Listeners for the select, with flowEnabled set to false, the "pointerdown" event is defined like this. This is exactly the same for the select in your codepen. However, when I remove the two "calcite-list" event listeners, the select starts to work. When I set flowEnabled to true and the select works as expected, I don't see those two "calcite-list" events in the "pointerdown" listener. I'll explore some more and see what I can come up with. In the end, I'll be using the item panel with the flowEnabled option set to true, which will be the best workaround for this issue.

‎03-01-2024

Hi @Sage_Wall. I forgot to mention that I'm using CDS 2.5.1. I tried changing versions, but it did not change the select behaviour. Your codepen is fairly accurate. One, and probably the only, difference I can see, is that I added more than one component to the item panel, i.e. an array of div components containing different functionality, of which one div contains a select dropdown. As I mentioned in my question, when I drag the layer list item outside of the group layer, the select suddenly works as expected.

‎03-01-2024

With the 4.29 release of the API, the LayerList widget has also been modified. I have a Layer List widget with group layers, where individual layers are added to different group layers. Custom content is then created for each layer (not group layer) when it is added (listItemCreatedFunction) and the content is added to the Layer List Item Panel, where some layer settings and functions can be performed. A "calcite-select" element is also added to the list item panel, which worked fine in 4.28, but it would not open and show the list options in 4.29. This only happens for layers inside the group layer of the Layer List widget. If I drag that layer to outside of the group layer and it becomes part of the main layer list, the select dropdown works. My workaround option, which I actually prefer now, is to set the layer list item's "flowEnabled" property to "true", which then opens the layer list item panel inside a "calcite-flow" item inside of the layer list widget. Is there some other setting I can look at to enable the select dropdown to work for the layer inside of the group layer?

‎02-10-2024

Thanks @RWaterman for the clarification. I'll make sure to follow any updates on the service.

‎02-08-2024

I am using the Sentinel-2 L2A image service (https://sentinel.imagery1.arcgis.com/arcgis/rest/services/Sentinel2L2A/ImageServer) in ArcGIS Pro and Javascript client. The values of the indices (from the available processing templates) are significantly lower than the values calculated from the raw downloaded Sentinel-2 L2A imagery. For example, NDVI ("NDVI Raw" processing template) values are typically in the range of 0.1 to 0.2 lower than it should be. I have also tried calculating the NDVI and other indices from the individual bands, but the result is the same. Is there an issue with the baseline processing?

‎12-01-2023

The duplicate IDs warnings are generated when strict HTML guidelines are applied by the browser, which is fine with me. The calcite-block chevron toggle buttons should not have the same ID of "toggle", but instead just the "toggle" class, which would be similar to the calcite-accordion-item chevron dropdown button. So maybe the Calcite team can have a look at this for future releases @KittyHurley ?

‎11-29-2023

Hi @MattDriscoll. I'm not able to recreate the results outside of my existing code base. Noted that the elements with the same IDs are indeed in a different DOM root. The first line of the warnings is this: [DOM] Found 24 elements with non-unique id #toggle: (More info: https://www.chromium.org/developers/design-documents/create-amazing-password-forms) Which led me to observing the following: I have a calcite-input element of type "password" inside a calcite-modal (hidden at startup). If I change the calcite-input type to "text", the ID errors do not show up. If I set the type back to "password" after the page has loaded, the ID warnings immediately appear in the console. It also seems that the issue is related with the autocomplete property of the input.

Online Status	Offline
Date Last Visited	12 hours ago

My Ideas

Latest Contributions by FC_Basson

Re: Graphics Layers not showing in MapView - possible graphics card issue

Re: Graphics Layers not showing in MapView - possible graphics card issue

Graphics Layers not showing in MapView - possible graphics card issue

Re: Select Dropdown in Layer List Item Panel not working inside group layer

Re: Select Dropdown in Layer List Item Panel not working inside group layer

Re: Select Dropdown in Layer List Item Panel not working inside group layer

Re: Select Dropdown in Layer List Item Panel not working inside group layer

Re: Select Dropdown in Layer List Item Panel not working inside group layer

Re: Select Dropdown in Layer List Item Panel not working inside group layer

Re: Select Dropdown in Layer List Item Panel not working inside group layer

Select Dropdown in Layer List Item Panel not working inside group layer

Re: Sentinel-2 L2A Image Service indices values too low

Sentinel-2 L2A Image Service indices values too low

Re: Non-unique IDs created for collapsible calcite-block chevron button

Re: Non-unique IDs created for collapsible calcite-block chevron button

AGOL custom web map URL parameters not working for...

Re: Features Component close event error - removes...

Re: Graphics Layers not showing in MapView - possi...

Re: Graphics Layers not showing in MapView - possi...

Re: Graphics Layers not showing in MapView - possi...