Latest Contributions by dotMorten_esri

It looks like there's a scaling factor issue at play, comparing to the text size in the browser window behind it. Are you using the newer Webview2 browser? Or the older IE7 based one that is built into WPF? ... View more

The dialog is hosted by the portal you're accessing and as such is just the size of the HTML returned by the server. Generally I'd use a smaller window to host the HTML content to better match the HTML content returned. ... View more

Different credentials for the same host at the same time is not something that the maps sdk supports. I'd be curious about the use-case for this, as we don't expect a user to be multiple different users at the same time. ... View more

This issue has been resolved in the v200.4 release that was just released. ... View more

Just wanted to add that sample uses the new GeometryEditor introduced in 200.3. The old SketchEditor that was available in 100.15 did not fully support multi-part geometries. ... View more

The exception you're pointing to shouldn't be an issue - this can occur deep down the .NET networking stack when a request gets cancelled, but it should _not_ lead to an application crash. It's merely a first-chance exception, and just how .NET does network requests. Did you by any chance enable that exception in the error-list to break on first chance exceptions of this type? Are you actually seeing an application crash if you just continue? (or run without the debugger attached) ... View more

First thing to note is we require minimum Windows build 19044 in 200.3 (19041+ SDK). Could you share what you have in your csproj file? Are you overriding runtime identifiers or Platform/PlatformTarget in that project? If you use our project templates and create an ArcGIS WPF project, does that work and how does it differ from your project? ... View more

We're currently experimenting with a code analyzer that'll help remind you to add this call. Would this be helpful?   ... View more

Glad you figured it out. If you find this step annoying too, please go upvote this issue: https://github.com/dotnet/maui/issues/7258 ... View more

The specific field types the error is referring to are quite new, and we're currently working on adding support for these in the native Maps SDKs. ... View more

You could also consider replacing your system's location driver with a NMEA based one. Of course that requires system-wide install and managing the connection outside your app. Windows won't "just" use a GPS dongle as its system location without some configuration/driver setup. Wrt UWP and serial ports, there's plenty of device information APIs to help you find the "right" port based on device ids. https://learn.microsoft.com/en-us/uwp/api/windows.devices.serialcommunication?view=winrt-22621 The device information will allow you to identify the same device regardless of it's assigned portname dynamically. The UWP version of the NMEA constructor takes that device information object directly as an input: https://developers.arcgis.com/net/api-reference/api/uwp/Esri.ArcGISRuntime/Esri.ArcGISRuntime.Location.NmeaLocationDataSource.FromSerialPort.html#Esri_ArcGISRuntime_Location_NmeaLocationDataSource_FromSerialPort_Windows_Devices_Enumeration_DeviceInformation_System_Nullable_System_UInt32__   ... View more

> Can we programmatically determine if the location is Fresh You can use the IsLastKnown property to check whether it is an old cached location. You can also look at the timestamp. > Presumably both APIs should return the same co-ordinates. We're not using the same API. You're using GeoCoordinateWatcher which is built on the older Windows Location APIs that has been deprecated. We're using WinRT's more modern GeoLocator in the Windows.Devices.Geolocation APIs, which might also be pulling from IP, WiFi, Celltowers etc to get a quick first location fix. You should be able to tell the origin of the location in the AdditionalSourceProperties property, although it is a bit dependent on your system's Location driver whether that'll get populated. The HorizontalAccuracy property might also be an indication of what kind of location fix you got.   > I'm comfortable that the projection is correct (it works the rest of the time). I just wanted to rule this out completely. It's a lot easier to troubleshoot if we remove all the extra stuff, just in case - grid transformations can be finicky and a web site is not guaranteed to use the exact same transformation data or calculation as the Maps SDK, and even the Maps SDK can be configured to perform the transformations differently depending on scenario.   ... View more

>  but we log the Easting and Northing Just to rule out any projection differences, could you instead verify that the original unprojected coordinate matches what you see in powershell? The projection used in Runtime might not match 100% the one you compare with online (or use Runtime to convert your powershell-based location using the same reprojection code and datum transformation steps).   We use the newer GeoLocator, (GeoCoordinateWatcher is based on a deprecated underlying location API) but there are various accuracy settings that might affect it too (we explicitly set it to high), and you seem to just be pulling the coordinate from the location. The very first location we get might be up to an hour old (the property on the location will indicate that and the dot on the map will be gray), but next location event should be "fresh". ... View more