Latest Contributions by deleted-user-iPdcWUgWcsoy

I've got the same problem. I've tried to add the FeatureTable to different dom nodes or layout widgets and I still get this problem. Now my workaround is to delete the "_trailingPaneNode" of this widget. var myFeatureTable = new FeatureTable({     featureLayer : featureLayer,     map : this.map,     syncSelection : true,     outFields: ["*"] }).placeAt(this.domNode); myFeatureTable._trailingPaneNode.destroy();‍‍‍‍‍‍‍ Somehow there is a problem with some style or something in this node. After I delete this node I can interact with the widget. ... View more

Unfortunately there are still no drawing tools (module "DrawToolbar") with 4.3. ... View more

Thanks again for your reply.   The main problem is, that we just startet an implementation of a web app with about 40 or 50 widgets with 4.0 beta. At this beginning we used "esri/widgets/Widget"! But this base class had such big changes with 4.2 that we can't use it at this moment. Till 4.1 we could handle the new changes somehow. The migration will cost too much time. I think for this reason the module "esri/widgets/Widgette" was introduced for migration issues.   I see that there is no option to merge these two base widget modules. So we have to migrate. odoe it would be nice that "esri/widgets/Widgette" can be kept in the next one or two releases. That will give us the time to migrate all widgets. Is it possible? Thanks in advance. ... View more

As I heard on Developer Summit in Berlin last year, it will be available in 4.3. Can't wait for it, too. Perhaps we will see next month before the Developer Summit in Palm Springs would start. ... View more

Thank you for your reply. I tried your last option of creating the ContentPane, add it to StackContainer and use the automatically created domNode of ContentPane as the 'container' property. Unfortunately the result is just like the same as before. I get a string representation of a widget (currently inherited from "esri/widgets/Widgette") which are inside my custom widget. Am I missing something? Here is my code snippet. This is a module that handles adding and removing to and from the StackContainer. // some code before... // 1. Create the Helper-ContentPane. var content = new ContentPane(); // 2. Add it to StackContainer and select it (this.navigationStack is type StackContainer). this.navigationStack.addChild(content); this.navigationStack.selectChild(content); // 3. Just check id and domNode property. console.info("content.id", content.id); console.info("content.domNode", content.domNode); // 4. Set container property as domNode of ContentPane. component.container = content.domNode; // ...some code after‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ The result is this. I debugged the widget handling and saw that this is the result of some core inheritance from dijit/_WidgetBase (toString function) which is used in esri/widgets/libs/maquette/maquette.js if there is no property 'vnodeSelector' while appending children in this custom widget. Here is the snippet of this part. let toTextVNode = (data: any): VNode => {   return {     vnodeSelector: '',     properties: undefined,     children: undefined,     text: data.toString(),     domNode: null   }; }; let appendChildren = function(parentSelector: string, insertions: any[], main: VNode[]) {   for (let i = 0, length = insertions.length; i < length; i++) {     let item = insertions[i];     if (Array.isArray(item)) {       appendChildren(parentSelector, item, main);     } else {       if (item !== null && item !== undefined) {         if (!item.hasOwnProperty('vnodeSelector')) {           item = toTextVNode(item);         }         main.push(item);       }     }   } };‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ So we use a custom main Widget with "esri/widgets/Widget" which contains one or more widgets inherited from "esri/widgets/Widgette". I know, the mixture of Widget and Widgette is not a nice solution but for some issues till now we have to use this base module and want to migrate later to esri/widgets/Widget. Are there any other solutions or hints? ... View more

Ah, ok I see. Every time I call 'this.scheduleRender()' in my custom widget, the 'render' function executes. So I have to manage some attributes, variables and/or globals so that there will be a different result in the render function. Is that right? Does anybody have some further hints and tips? ... View more

Great thank you! I will check your samples but I think I can take advantage of it. We are now to deep in this thing. So we will use it like you do ;). Our plan is (and I startet that meanwhile) to use ViewModels written in JavaScript and use them in widgets written in TypeScript. Can I contact you for some more questions or should I open new separate threads? ... View more

odoe‌ Ok, now here is my reply. Unfortunately there is no comfortable way to develop our widgets without TypeScript. So we have to start nearly from scratch. Doh! So I have two questions. 1. Do you have a nice documentaion where I can find some hints to start with Widget development including Accessors/ViewModels from scratch? I'm really new to that stuff and I need to develop some widgets really soon. I read the documentation from the Esri site here, here and here. I need some more information please. 2. How many main changes will be happen in the future releases of the API? For every update we need several of days and weeks to get our application runnable again. Thanks in advance. Regards Martin ... View more

Hey Rene, thanks for your reply. I hoped, that you will be the one who answer my question! We have built our application since 4.0 was released. So we implement our widgets straight forward without TypeScript in the recommended way of ViewModels to the best of our knowledge and belief. I will check your hint/link if we can take some advantages for our widget development and will give a reply here. ... View more

Hello again, could anybody share it with an Esri staff? I appreciate any help! This is really important for us and planning with the ArcGIS API 4.2 for JavaScript. Regards Martin ... View more

Indirectly, this is a Bug in the JSAPI as AJ Morris said. The problem is, that since ArcGIS for Server 10.2(.2) there is no spatial reference in the returning geometry of identify result. In ArcGIS for Server 10.1 the spatial reference still exists in identify result. So perhaps the JSAPI takes a default spatial reference for returning geometry which is 4326 (WGS84) and not the requested one. So I thing there is a bug in ArcGIS for Server 10.2. But the solution described above works for me too and is a good workaround. So thanks ! ... View more