Latest Contributions by AndyGup

Hmmm, the multiple calls are most likely related to the toggle function, it shouldn't really be there. A better approach would be to remove toggleI() and any other state management/business logic from the widget and only use plain old data binding. That way the View is only used as a View. The component should handle all state management and business logic. So in the widget you'd have: @property() message = "Start"; //default value render() { return ( <div>{this.message}</div> ); }     ... View more

We don't have any examples of custom widgets in Angular, but you can build them. How you build them depends on whether you are using JavaScript or TypeScript. And, it will be easier if you are using Angular 11+ because then you can use the APIs ES modules (npm @arcgis/core) Here's another conversation about TypeScript widgets: https://community.esri.com/t5/arcgis-api-for-javascript/handling-and-rendering-in-a-widget/m-p/1073956#M73686. and scroll down towards the bottom. A couple of items to note: * Build your widget in .tsx (if using TypeScript + Angular) * In tsconfig.json set "jsx": "react", "jsxFactory": "tsx"    ... View more

Just a quick follow-up, I tested the above code and it worked. Here's some more psuedo-code:     //Add widget to component this.simpleWidget = new SimpleWidget2({ container: document.createElement("div") }); // Be sure to add widget to the view this.view.ui.add(this.simpleWidget, "bottom-right"); // After map initialized and widget has been added to the component let count = 0; const c = this.simpleWidget.container.addEventListener("click", () => { this.simpleWidget.msg = "test" + this.count++; })       ... View more

Yep, getting closer. There is still state management in the render() method, you'll need to move the button click event listener code to the component.  Some other suggestions, note this is psuedo-code because I haven't tested it:       import Widget from "@arcgis/core/widgets/Widget"; import { subclass, property } from "@arcgis/core/core/accessorSupport/decorators"; import { tsx } from "@arcgis/core/widgets/support/widget"; @subclass("esri.widgets.SimpleWidget2") class SimpleWidget2 extends Widget { @property() msg = "test"; //to test simply assign this property a different string. private _toggle(){ return this.msg; } render() { const testMessage = this._toggle(); return ( <div> {testMessage} </div> ); } } export default SimpleWidget2;         ... View more

Hi @litch it's best to avoid setting up any state management in the render() method. One recommendation is to move any state management code (e.g. onMapChange) into the postInitialize() stage of the widget's life cycle.  You can implement postInitialize() just like you can with render(). Here's some additional Widget-related documentation you can read through, if you haven't done so already: https://developers.arcgis.com/javascript/latest/custom-widget/#implement-properties-and-methods.  ... View more

One suggestion is to get your basic app running in Vue without capacitor: https://github.com/Esri/jsapi-resources/tree/master/esm-samples/jsapi-vue-cli. That will help identify any non-Capacitor related performance issues. Also be sure to check out the system requirements documentation: https://developers.arcgis.com/javascript/latest/system-requirements/#hardware-requirements.   ... View more

Hi @JohnRegan this sounds like a configuration issue. Do you have a basic github repo you can share that reproduces the issue? ... View more

This sounds like a life-cycle issue with the mapping component. If you are using ngOnInit() you might need to try switching to using ngAfterViewInit(). ... View more

Hi @JethroLeevers since it is a parse error, one thing is to make sure you have this set:  https://github.com/Esri/jsapi-resources/blob/master/4.x/amd/dojo/build.profile.js#L491  ... View more

Hi @NilankaD the angular-esri-map project was fully retired in November 2020: https://github.com/Esri/angular-esri-map#angular-esri-map Also, note that Google does not support that version of Angular anymore, currently they only support version 9+: https://angular.io/guide/releases#support-policy-and-schedule. I suggest trying to get the ArcGIS JS API 4.19 functionality working in a non-Angular vanillaJS app and then migrate that code back to your Angular app. We typically only offer samples that work with the latest versions of a particular framework, and where possible we now recommend upgrading from using the APIs AMD modules to using ES modules. Here's a sample using Angular 11 (soon to be upgraded to Angular 12): https://github.com/Esri/jsapi-resources/tree/master/esm-samples/jsapi-angular-cli  ... View more

@Jay_Gregory  since you mention that the JS API works and axios doesn't, this is most likely an issue with axios adding a header field that is triggering preflight rather than a problem with your ArcGIS Server install. I'm not familiar with axios, but my suggestion is figure out what header field is being added that is causing the problem and remove it. The best way to do that would be to compare the axios request headers with the JS API headers.  ... View more

Hi @GiovanniVanore1 that error looks like it has something to do with your Angular configuration. I tried your code in our Angular ESM sample and it worked: https://github.com/Esri/jsapi-resources/tree/master/esm-samples/jsapi-angular-cli.  ... View more