POST
|
@NicholasRolstad2 , I am glad you were able to get this resolved! You don't have to do this for non-editable layers, since Editor will know which layers are not editable. The only way non-editable layers can show up in Editor, is if you are signed in as the data owner or an admin. Otherwise, they will not be available to be selected or to create features. If you are seeing non-editable data show up in Editor, please let us know and ideally provide an example. Thanks! Jose
... View more
07-28-2025
12:16 PM
|
1
|
1
|
152
|
POST
|
Hello @NicholasRolstad2 , Appreciate the feedback, we will work on updating more of our editing samples to use map components. In the meantime here is a codepen for grabbing a layer in a webmap, and disabling editing using the Editor.layerInfos. https://codepen.io/banuelosj/pen/gbawaop Thanks, Jose
... View more
07-25-2025
03:05 PM
|
0
|
3
|
202
|
POST
|
@NicolasGIS , Thank you for reporting this! This was found to only be reproducible in version 4.32. This has been resolved, and will be fixed in the next release 4.33. Thanks! Jose
... View more
04-15-2025
07:36 AM
|
1
|
0
|
243
|
POST
|
Hello @maiam , Thank you for your question. We added support for viewing related records in subtype group layers in our last release of MapViewer. That means it will be available in 11.5 Enterprise. The post you are referring to was in regards to supporting related records for feature layers and map image layers. Subtype group layer support was just added. At 11.5 you will be able to see the option to view related records in the popup for the sublayers of the subtype group layer, as you described you could do for the feature layer case. Fortunately, 11.5 is also a recommended Enterprise release for utility networks, as we have been working on numerous features to further enhance our current support of utility networks on the web. Thanks! Jose
... View more
01-17-2025
12:50 PM
|
3
|
1
|
830
|
POST
|
@DavidOke , The team also would like to mention that accessing view.grid directly is not recommended. This has not been documented yet, as the API is likely to change.
Thanks,
Jose
... View more
11-19-2024
07:54 AM
|
0
|
1
|
482
|
POST
|
@DavidOke , It will be on the app to hide the grid before calling destroy on the widgets that utilize the GridControls. This means Sketch, Editor, SnappingControls, and GridControls. The way to hide the grid in Sketch is the following.
Sketch.snappingOptions.gridEnabled = false;
This is necessary because the grid lives in the view, and multiple widgets may be utilizing the grid. If we destroy one widget, the other widget maybe using the grid, so removing the grid would not be ideal in this scenario. We will be working on improving this experience for better widget communication, but at least for now this is how you can hide the grid.
Thanks! Jose
... View more
11-18-2024
01:52 PM
|
0
|
0
|
491
|
POST
|
@FC_Basson This regression has now been resolved in the upcoming release of 4.29! Again we appreciate you reaching out to inform us of this. You can continue to rely on the immediate-click, just know the issue has been resolved. Thanks, Jose Banuelos
... View more
01-10-2024
09:12 AM
|
3
|
0
|
3920
|
POST
|
@FC_Basson , I am glad this works for your use case. I took a look at the codepen, and the "immediate-click" will work well in this situation. We did find that this is indeed a bug, and we have logged an issue internally. We will look to provide a fix for 4.29 for the single click event listener issue. In the meantime you can continue to use the recommended "immediate-click" event listener until we provide the fix or you can continue to use this recommended workflow indefinitely. Thanks! Jose
... View more
11-14-2023
07:34 AM
|
1
|
1
|
4049
|
POST
|
@FC_Basson , Appreciate you reaching out to relay this difference in behavior from the last release. Would you mind providing a codepen with a simplified example of your use case? Code snippet would work as well, we just want to make sure we account for your use case while we investigate this. We had an initial recommendation of relying on the view "immediate-click" event instead of the "click" event whenever you are actively drawing, whether it was 4.27 or 4.28. However, we want to make sure we understand your workflow to guarantee our recommendation works in your case as well. Thanks! Jose
... View more
11-09-2023
09:49 AM
|
1
|
0
|
4097
|
POST
|
@Lerman Thanks for reporting this issue, we are using a modal in the widget, and this is causing the underlying issue. We logged an issue internally, and will be replacing this modal with another component within the widget to provide the same message, but prevent this issue from occurring. Thanks! Jose
... View more
07-17-2023
03:46 PM
|
1
|
1
|
1074
|
POST
|
@JimmyBowden , This issue currently hasn't been addressed. This feature was pushed due to the SubtypeGroupLayer work we have implemented in the last two releases. We added webmap reading support for SubtypeGroupLayer in 4.25, and we worked on editing support for this layer type for this upcoming release. This is an ongoing project we plan to implement this year. This will affect the entire API, since the goal is for all widgets and API components to support Subtypes, not just the popup. And I accidentally marked your last post as a solution, so I apologize for that. I'll get that resolved.
... View more
02-09-2023
04:42 PM
|
0
|
1
|
1212
|
POST
|
@Anonymous User , This is a great question. Unfortunately, selecting and updating vertices is not very keyboard accessible with our API at the moment. This is good feedback for us to to explore this avenue further. Do you happen to have a use case for this enhancement request that you could share with us? Are you developing an application that would really benefit from this? I understand the accessibility need, we just like to also have real life scenarios to tie to these enhancement requests. Appreciate your feedback, Jose
... View more
12-19-2022
02:38 PM
|
0
|
3
|
2454
|
POST
|
@Anonymous User , This is a bug that was introduced at version 4.21. This was just unfortunately not caught earlier, so I apologize for that. I have logged an internal bug, so hope we can get this resolved in our next release. If you change the version to version 4.20 in the sandbox link you provided, you can see it working. Thanks, Jose
... View more
12-19-2022
09:51 AM
|
1
|
6
|
2470
|
POST
|
@RyderRoss , This is indeed resolved in 4.24! We improved snapping and went with a lazy-load approach to creating FeatureSnappingLayerSources. Therefore, there will not be any extent queries unless a user manually checks the layer on for snapping or programmatically sets it in the SnappingOptions.featureSources collection. Please feel free to try it out and report any issues you find. Thanks! Jose
... View more
06-28-2022
03:58 PM
|
0
|
0
|
1989
|
Title | Kudos | Posted |
---|---|---|
1 | 07-28-2025 12:16 PM | |
1 | 04-15-2025 07:36 AM | |
3 | 01-17-2025 12:50 PM | |
1 | 01-04-2022 09:52 AM | |
3 | 01-10-2024 09:12 AM |
Online Status |
Offline
|
Date Last Visited |
07-29-2025
03:49 PM
|