Latest Contributions by MichaelLev

Dear Majdoleen Awadallah, Does your workbench create the correct output as you expect (I mean, there are 2 aspects: 1. To create the wanted file format, 2. Covert coordinate systems, if needed)? If positive, Then you need to - link the source to e.g. 'SourceDataset_ACAD' user variable name, - link the result to e.g. 'FME_SHAREDRESOURCE_DATA' server variable Then after publishing it to fme server (I use fme cloud) you need to learn and adapt the code in FME Server Playground - Upload File In Session so it will fit within your web application. Do you develop web application or Web AppBuilder custom widget? Do you use 2D or 3D ? I'm doing the 2nd option with 3D Scene. I managed to activate the exaple code within my web app and my fme cloud with my input and output formats and coordinate systems (I don't need to insert the result file into a map in my example web app), and now in midst of developing and debugging the custom widget stuff, where I'll have to insert the result into the 3D web scene. Advice: Referring the fme stuff - I have asked questions in fme community (of e.g. fme cloud) and got serious help. In addition, if the company you work in has licence for the fme workbench, you are entitled help from the fme-agency that sold the workbench to your company. Michael. ... View more

Dear Robert, Thank you very much! You always save my day! It works! Only I found that in order to get the alert when I re-open the in-panel widget, I have to reset "isOpening" inside setTimeout: onOpen: function () {     if (!this.isOpening) {         this.isOpening = true;         let missing = [];         // ... code lines to test parameters         if (missing.length !== 0) {              let errMsg = `missing config param${missing.length > 1 ? "s" : ""}: ${missing.join(", ")}`;             alert(errMsg);         } else {             // code lines to do if parameteers are OK         }         // close widget         setTimeout(lang.hitch(this, function () {             this.isOpening = false;             //PanelManager.getInstance().closePanel(this.id + '_panel');             WidgetManager.getInstance().closeWidget(this); //best way to close         }), 300);     } }, // eof onOpen() So, now it works - thank you for explaining that closing the widget from within onOpen() creates race conditions, and for showing how to handle it. If I may only ask, I wish to also get explanations: What is the function of "isOpening" property? What exactly is the cause of the race conditions? and how does the setTimeout handle it? Only in first opening, I got my "exact expected behaviour" -      at first, the widget icon shifts up, then, I see the alert ,then, the widget icon shifts down  but in all successive openings,      first I see the alert, and only AFTER the alert, the widget icon shifts up, then shifts down. So, In order to always get my "exact expected behaviour"     I had to "wrap" the whole contents of onOpen() inside an additional setTimeout (not shown in the above code). I assume that this is connected smehow to the same race conditions? Why if I use "closePanel(this.id + '_panel')" instead of closeWidget(this), I get an unwanted behaviour - I do see the alert only on each 2nd click of the widget? With appreciation, Michael ... View more

Dear Majdoleen Awadallah, Please see also my answer to Carlos there. ... View more

Dear Carlos, Thank you! I'm in midst of doing it by another way - using fme cloud server (and workspace buit in fme workbench). I'll update you when I've come to conclusions. Michael ... View more

Dear Robert, Thank you! As usual, your help is very effective and helpful -          I succeeded to open LayerList widget from within my slice custom widget          by learning from WAB example stemapp/widgets/samplewidgets/WidgetCommunication - THANK YOU! note:  In order to have LayerList widget work under API 4.16 I had to remove 'dojo/i18n!esri/nls/common'           from define and apiNlsBundle from function arguments. It works.           I see t's not needed in 4.16, though I'd like to know what it is? and why it's not needed anymore in 4.16 ? Michael ... View more

Dear Robert, I'm debugging my slice custom widget and it works, however I have questions concerning the UI code needed for displaying the LayersList: In esri example BuildingSceneLayer with Slice widget | ArcGIS API for JavaScript 4.16  There is the paragraph to display the layers list at top-left       // Add a layer list widget       const layerList = new LayerList({             view: view       });       view.ui.empty("top-left");       view.ui.add(layerList, "top-left"); Since the slice widget popup itself is displayed at top-left, I want to display the layers list at bottom-right, so I write (in the widget.js)       this.sceneView.ui.empty("bottom-right");       this.sceneView.ui.add(this.layerList, "bottom-right"); but the whole this.sceneView.ui is hidden since class esri-ui-corner-container is hidden which is the father of the 4 corners. and top-left corner is not empty. My questions: 1. How should I handle correctly the display of the layers list?     Below are the 4 lines I did, but maybe there is a cleaner and nicer way?:               this.sceneView.ui.empty("bottom-right");               this.sceneView.ui.add(this.layerList, "bottom-right");               document.getElementsByClassName("esri-ui-corner-container")[0].style.display = "block";               document.getElementsByClassName("esri-ui-top-left")[0].style.display = "none";      And I don't know yet why top-left of esri-ui-corner-container is not empty already but has some widgets in it? 2. Could I (how?) display the layerslist in a popup that the user can drag upon the screen (or even minimize and maximize?) I'll appreciate your help ... View more

Dear Robert, Thank you! I've succeeded to activate my in-panel custom widget (which is based on API 4.16) by learning from your zip of screenshot and from more widgets, and to to solve most my bugs, and I'm continuing debugging. Michael ... View more

Shay, I've succeeded to solve most my bugs... I'm continuing debugging. Thank you! Michael ... View more

Dear thejus kambi, I'm facing same problem. I added some custom widget in the widgets-panel and have the same error. Perhaps because my widget use API 4.16, maybe not all needed classes are loaded in time?? You wrote "To fix it, I included the measurement widget in the require present in the html page. this ensured that the required js are retrieved before it loads my custom widget.". Please explain since I don't understand what to do - which is this html page and what exactly to write there. Thanks, Michael ... View more

Thanks, Shay! To answer your curiosity - I changed 3 lines above your line - I canged: var apiVersion = '4.15'; to 4.16 but it was not enough. After seeing your doc link, I changed both apiVersion  to 4.16 and also apiUrl within the comment. I saw that if I download the app from within WAB, the apiUrl is uncommented within the zip, And I saw also that if I click the launch button of the app from within the WAB, it also uses the 4.16 API, due to apiVersion var. So, indeed I solved the problem how to run on 4.16 My problem now is an error in my slice widget, but I don't know how to debug and find it. screenshot attached Could I attach zip of my in-panel widget code? Michael ... View more