Latest Contributions by AndyGup

‎08-15-2022

Hi @ViktorSafar you can't really mix React/TypeScript with our JS API Widget framework. To work around that try the following to allow the widget to parse correctly: // @ts-nocheck /** @jsxRuntime classic */ /** @jsx tsx */ import Widget from "@arcgis/core/widgets/Widget"; import { subclass } from "@arcgis/core/core/accessorSupport/decorators"; import { renderable, tsx } from "@arcgis/core/widgets/support/widget"; // import React from 'react'; @subclass("esri.widgets.HelloWorld") class HelloWorldWidget extends Widget { render() { console.log("rendering") return ( <div id="myhello"> HELLO </div> ); } } export default HelloWorldWidget; I also recommend updating your package.json browserslist to minimize transpiling: "browserslist": { "production": [ "last 1 Chrome version", "last 1 Firefox version", "last 2 Edge major versions", "last 2 Safari major versions", "last 2 iOS major versions", "Firefox ESR" ], "development": [ "last 1 Chrome version", "last 1 Firefox version", "last 2 Edge major versions", "last 2 Safari major versions", "last 2 iOS major versions", "Firefox ESR" ] }

‎08-10-2022

Hi @rogenjh Here's a basic codepen using reactiveUtils to show the concept: https://codepen.io/andygup/pen/ZExjMZq?editors=1000. MapView.interacting might be a better property for your use case. We recommend using reactiveUtils instead of watchUtils, here's the doc https://developers.arcgis.com/javascript/latest/api-reference/esri-core-reactiveUtils.html. watchUtils have been deprecated.

‎08-05-2022

Hi @thanasiskoubaros are you using a self-hosted proxy? The only way to troubleshoot a proxy is by accessing the server where the proxy is hosted. 1. Check the proxy web server logs for hints at what the problem might be. 2. If the web server logs look normal, use tools like Fiddler or Charles Debugging Proxy to analyze and validate the request/responses to and from the proxy.

‎07-26-2022

@jasonwriterhave you checked out this sample https://developers.arcgis.com/javascript/latest/sample-code/watch-for-changes-reactiveutils/ ?

‎07-22-2022

Hi @SriharshaK are you using Webpack 4? If so take a look at this Known Issue and see if the information applies: https://github.com/Esri/jsapi-resources/tree/master/esm-samples/webpack#known-issues

‎07-19-2022

@BobCowling2 quick update on your original posting above, I've created an enhancement request to add an accuracy circle and compass heading symbol to the Track Widget.

‎07-19-2022

Thanks @james-rae for the heads-up. I've put in an enhancement request to use a less generic naming convention for that variable. [Update: we won't be able to fix that variable until we drop WebGL1 support, possibly next year 2023. It's a built-in GLSL macro used for checking the current GLSL version.]

‎07-18-2022

Hi @BobCowling2 Can you get us the support ticket number? Thanks for the additional info. We aren't sure yet where the issue is occuring. We compared code between our Widget and Mapbox GL JS. The only difference is we set high-accuracy by default: https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Track.html#geolocationOptions.

‎07-15-2022

Hi Bob, do you know if your organization has a tech support contract, and if there is someone else that can open a ticket for you? I'm not sure what a bug report is. This is one of those instances where we need to get tech support involved to capture detailed information about your configuration, your phone, etc.

‎07-15-2022

Hi Bob, it seems like this is a duplicate post. let's move the accuracy discussion to this other thread => https://community.esri.com/t5/arcgis-api-for-javascript-questions/poor-accuracy-of-locate-widget/m-p/1192491#M77928

‎07-15-2022

Hi @BobCowling2 thanks for reaching out, can you please open a support ticket? That way they can gather all the necessary information from your set up. The bouncing around might be related to spurious location values not being filtered out.

‎07-11-2022

Hi @DamonDamon here are Mozilla's guidelines for trying to address problems similar to yours: https://support.mozilla.org/en-US/kb/upgrade-graphics-drivers-use-hardware-acceleration. Have you looked into this?

‎07-11-2022

Hi All, Please provide a simple GitHub repo that reproduce these errors so that we can investigate your issue. We recommend you start with one of our ES modules samples: https://github.com/Esri/jsapi-resources/tree/master/esm-samples. "unexpected token" errors are very common in JavaScript. It's related to a parsing error in the code. With JavaScript frameworks, this is most commonly caused by configuration issues.

‎07-05-2022

@turbolego can you share your package.json and tsconfig here? Also, please retest using the .browserslistrc file I link to above, and then try setting your tsconfig to target ES2020.

‎07-05-2022

Hi @Anirban_Banerjee we recommend using ES modules "@arcgis/core" with new React projects rather than esri-loader. Here is a working example: https://github.com/Esri/jsapi-resources/tree/master/esm-samples/jsapi-create-react-app.

Online Status	Online
Date Last Visited	5 hours ago

My Ideas

Latest Contributions by AndyGup

Re: Custom widget error

Re: Unit Testing with WatchUtils

Re: World_Basemap_v2 fail to display

Re: reactiveUtils

Re: arcgis/core library failing after update

Re: ArcGIS JS API 4 Locate widget like WebAppBuilder

Re: Build error with @arcgis/core and Angular 11: "Module parse failed: Unexpected token"

Re: Poor Accuracy of Locate Widget

Re: Poor Accuracy of Locate Widget

Re: ArcGIS JS API 4 Locate widget like WebAppBuilder

Re: Poor Accuracy of Locate Widget

Re: Issues with webGL performance and support

Re: Build error with @arcgis/core and Angular 11: "Module parse failed: Unexpected token"

Re: Build error with @arcgis/core and Angular 11: "Module parse failed: Unexpected token"

Re: React-based compilation error (Module not found and JSX related)

Re: Route not displayed after update to chromium 1...

Re: Route not displayed after update to chromium 1...

Re: problem with deploying calcite to cloudflare

Re: ArcGIS Maps SDK for JavaScript – Version 4.33 ...

Re: ArcGIS Map Components build/performance issues