Latest Contributions by JoelBennett

From the documentation: "To download the ArcGIS API for JavaScript and its documentation, navigate to the ArcGIS API for JavaScript download page and log-in with your Esri global account." I too use this to host the API on networks that have no internet access. ... View more

From your description, this appears to be a bug, but you shouldn't necessarily have to go through the effort of manually checking the vertices yourself.  One possible workaround may be to clone the polygon, and check the property of the cloned object.  Another workaround may be to call one or both of the following on the original geometry: geometry.notifyChange("rings"); geometry.notifyChange("isSelfIntersecting");   ... View more

I think what you're looking for is geometryEngine.contains: if (geometryEngine.contains(polygonGeometry, multiPointGeometry)) { //do something }   ... View more

The documentation states the height values are expected to be in meters.  Therefore, it appears that if you have measurements in some other units, you'll need to convert those values to meters first. ... View more

Note, this is only an issue when using (1) PictureMarkerSymbols with offsets, and (2) version 4.23 of the API.  It works fine in 4.22.  See also this post. ... View more

Somebody can correct me if I'm wrong, but the visibility of that section doesn't appear to be configurable.  Adding the following to the style tag of the "Edit features with the Editor widget" sample causes it to disappear though: div.esri-editor__scroller>div:first-child { display: none; } Perhaps you can work that selector (or something similar to it) into your application. ... View more

These are some great new features, and I'm continually impressed with the things that keep coming out each release. Many thanks to the team for all they continue to do to support us in turning out quality solutions for our customers. What I don’t doubt about 4.24 and subsequent releases is that they’ll continue to contain many powerful new features. What I do wonder about, on the other hand, is what they won’t contain. Although the "bonus track" in the original post isn't an official position, it does invite a particular discussion...specifically the part about some being "stuck on 3x", and therefore presumably not updating to 4x. For my part, I started making the jump with 4.16, and after a 6-month process, completed it, and released our framework with 4.18. The transition wasn’t the most pleasant experience, but still good and valuable nonetheless. But here’s the main point of this post: if I had waited until ESRI had migrated everything we needed from 3x to 4x, my organization would still be “stuck on 3x” to this day as well. For example, the 3x MapImageLayer, which we use heavily.  I’m aware about this recent post which says it’s targeted for 4.24, but I still mention it because it’s part of the larger point.  By now, this module has been “Coming Soon” for nearly five years.  I worked around its absence by writing my own implementation (which works, although is not ideal), but that isn’t necessarily an option for everybody else needing it. Another example is the ScaleDependentRenderer. It was another one I had to create my own implementation for, during which I quickly discovered 4x unfortunately doesn’t support custom renderers like 3x did. Nonetheless, although one of your own recently said that implementing scale-dependent rendering in 4x is “super simple”, it’s been "Under Consideration" for years. Other things that’ve made me wonder: There hasn’t been a single item that’s made the jump in the functionality matrix in about a year. The 3x home page once plainly said 3x would be retired in August 2022, but that notice quietly disappeared a few months after it showed up. ESRI is still actively seeking to introduce people to the 3x-based Web AppBuilder with a recent “overview and concepts” blog that’s newer than the corresponding one for Experience Builder by 8 months. All that is to say, from my limited outsider perspective, we seem to be getting some rather mixed messages. Is 4x parity with 3x no longer a priority? If it still is, is it expected to be reached anytime soon? ... View more

My bad, you are correct; this upcoming version looks like it's working properly in this regard.  We'll stick with 4.22 for now, and look forward to 4.24. ... View more

Thank you for the reply.  I'm not sure what the codepen is supposed to show though; the symbols aren't offset, and I don't think hitTest even comes into play. If a fix has already been applied in the "next" version, can you please tell me what modules have been affected?  I see the aforementioned "draw" function has been updated, but simply applying those changes does not resolve the issue.  ... View more