Latest Contributions by LefterisKoumis

Thank you. Huge oversight on my part not to add another async/wait at the beginning. ... View more

Thank you Jeff. However it does not do the intended purpose. I wanted each iteration to go through the esri request and do the calculations based on the response before it proceeds to the next iteration. The script provided, it goes through the sStates loop and then execute all promises in parallel (Promise.all). As I mentioned before, I wanted each iteration to run in series to grab the variable at #27 and uses at #6 before it proceeds to the next iteration. ... View more

Thank you Jeffrey.  I modified my script to explain better.  The esriRequest will produce a value (#27) which it will be used on #6 before the next iteration. The script presently will not pause the loop awaiting the processing of #6 in my script. Also in your script, I assume that there is no option on   #15 (second script) since you define options in esriRequest.   ... View more

THank you Ken. I don't think in my case it will work. I didn't explain my issue well. I changed my script.  THe esriRequest will produce a value (#27) which it will be used on #6 before the next iteration. ... View more

Thank you @KenBuja . I am surprised that there is no css to change background color of rows. Only when you hover over it or select it. ... View more

Hello @KenBuja . Where can see all available css properties for the feature table or all esri widgets? Thank you. ... View more

Hello @RobertScheitlin__GISP . It seems that the above suggestion does not work for feature table rows. Tried:  .esri-feature-table tr:nth-child(odd) { background-color: rgba(255,0,0,0.1); } .esri-feature-table tr:nth-child(even) { background-color: rgba(0,255,0,0.02); } Suggestions? Thanks. ... View more

ok. I had to change it a little bit. Since you are using points you don't have to worry about altering the geometry of the features like I showed on the video clip. The purpose of the return in the hittest is in case that you have more actions in the event. https://codepen.io/lkoumis1/pen/bGZEwxK  ... View more

Hello Nicholas. Sorry I forgot to include in the posting before line#5  editorVM.watch(['state', 'featureFormViewModel.feature'], () => { Also, for he hittest don't forget to include the return. I attached a short video that shows that after you create the feature it let you only edit the geometry of the feature you created and it won't let you another feature unless if you complete the fields. ... View more

Update. Until ESRI responds with a solution, I have this workaround. Please let me know if there are issues with this method. It was tested and it works as intended. Workaround: First create a global variable. I named it "creating" and set it to true. Then, set the variable to false when the user completes the sketch of the new feature.   if (editorVM.state == 'creating-features' && editorVM.featureFormViewModel.feature && editorVM.featureFormViewModel.state == 'ready') { editorVM.sketchViewModel.on("update", function (event) { if (editorVM.featureFormViewModel.state == "ready" && (editorVM.sketchViewModel.activeTool == "transform")) { creating = false} } _ _ _ _ _ _ _ _ _ _ _ _   Then, prevent the creation of new features by disabling the click event. Allow only reshaping the feature prior submitting.   view.hitTest(event).then((response) => { if (!creating) { if (!(editorVM.sketchViewModel.activeTool == "reshape")) { editorVM.sketchViewModel.cancel() event.stopPropagation return } } _ _ _ _ _ _ _ _ _ _   When the user submit the form for the feature, you can change the "creating" variable to true so you can create more features if needed.   editor.viewModel.featureFormViewModel.on('submit', _ => { creating = true _ _ _ _ _ _ _ _    @JB19 @NicholasWright  ... View more

create a calcite panel at the start or end and place the layerlist widget inside the panel.   ... View more