POST
|
I can imagine that this would not be an easy task. The PC in question is definitely older than 5 years. In the meantime, we have received similar issues from other clients, also with older PCs I suspect. I'll try to get the PC info for them too.
... View more
|
1
|
1
|
59
|
POST
|
Hi @Sage_Wall Here is an update to your codepen with the code that breaks the select (see line 51). https://codepen.io/fcbasson/pen/jORMyVy I want the group layers to not be sortable/draggable, but the sublayers can be sorted and dragged.
... View more
Thursday
|
1
|
2
|
70
|
POST
|
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)
... View more
Wednesday
|
1
|
0
|
145
|
POST
|
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 ?
... View more
|
0
|
7
|
249
|
POST
|
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.
... View more
a week ago
|
0
|
0
|
25
|
POST
|
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.
... View more
a week ago
|
0
|
1
|
40
|
POST
|
After removing all jQuery from my code, I am still experiencing the same issue with JS API 4.29 and CDS 2.6.0.
... View more
a week ago
|
0
|
3
|
50
|
POST
|
Thanks, I was actually just reading that blog. But still, with 4.28 all my jQuery was working fine.
... View more
2 weeks ago
|
0
|
5
|
57
|
POST
|
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?
... View more
2 weeks ago
|
0
|
0
|
116
|
POST
|
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.
... View more
2 weeks ago
|
0
|
0
|
140
|
POST
|
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.
... View more
3 weeks ago
|
0
|
2
|
163
|
POST
|
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?
... View more
3 weeks ago
|
1
|
19
|
313
|
POST
|
Thanks @RWaterman for the clarification. I'll make sure to follow any updates on the service.
... View more
02-10-2024
12:23 AM
|
0
|
0
|
84
|
POST
|
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?
... View more
02-08-2024
11:28 PM
|
0
|
2
|
167
|
Title | Kudos | Posted |
---|---|---|
1 | Friday | |
1 | Wednesday | |
1 | Wednesday | |
1 | Thursday | |
1 | 3 weeks ago |
Online Status |
Online
|
Date Last Visited |
9m ago
|