Latest Contributions by dotMorten_esri

‎11-09-2022

I'm fairly certain that text symbols always gets converted to vector CIM symbols. TextSymbols aren't great for sharing, since a certain device or PC might not have the font installed that the text symbol relies on, so those symbols are vectorized so it won't be an issue running on different systems.

‎10-20-2022

Reference scale will keep the same line width and get smaller and bigger with the zoom (without reference scale, lines usually keep their line width and only length changes), so I think this is the opposite of what you want. The line is there to represent a physical object from its starting point to its ending point, and as you zoom out those points will appear closer and closer. It sounds like what you're really looking for is the MarkerSymbol behavior, and you should consider highlighting the doors using a marker symbol instead. You might even be able to use both, so when you zoom in far, you use lines to represent the actual door, but when zooming out, using the scale range you switch to a marker symbol that represents the location of the door at the point where the line symbol becomes too small.

‎10-06-2022

Just to follow up: are there specific minimums you're required to support that isn't covered by the above? Also feel free to provide more feedback in the beta forums: https://esriurl.com/agsrt200beta

‎10-06-2022

Not quite. One thing to note though: framework target version and minimum supported version isn't the same thing. You can generally target the latest SDK for each platform, and still support older versions, and that's pretty much the case across all our target frameworks. The catalyst bit is a bit confusing - the OS version is different from the catalyst sdk version. I found a good list here: https://stackoverflow.com/a/69748714/1702326 Our minimum support there is 14.0 Wrt Windows minimum is 19041 in the beta, but we're currently considering changing our minimum supported from minimum support Windows version excluding LTSC versions (which is 19041) , to in the future include the LTSC versions still in mainstream support, which would bring the support all the way down to 17763 until 2024 (Note: v100.15 is 18362 so this increases the lower bound). You will still need to target 19041, but will then be able to set the minimum to 17763. For Android, the minimum isn't 31 - that's the target. The minimum is 26 for v200 (it was 23 for v100.15).

‎09-27-2022

Also consider changing the autopanmode to navigation or compass instead.

‎09-16-2022

Regarding this: protected override async Task OnStartAsync() { await GetLocation(); } This method shouldn't get the location. It should start monitoring for locations (ie start listening to an event source, or launch a thread that starts monitoring in a loop), and when locations gets updated, you call base.UpdateLocation. Stop async would then stop that thread (or unsubscribe depending on what you're getting locations from)

‎09-16-2022

My guess would be that when you set up the `event this.AssociatedObject.LocationDisplay.DataSource.LocationChanged` you're doing it to the datasource, before you're reassigning the datasource, but your code never checks is the datasource changes, where you'd then unsubscribe from the old one and subscribe to the new one. At least double check that this event handler is hooked up _after_ you assign the new datasource.

‎09-15-2022

Sort of. If you're using WPF you can definitely turn off the zoom box gesture completely and do your own thing (which would have to include drawing your own box). But no there's no way to repurpose the existing box that is drawn to do something other than zoom.

‎09-15-2022

There's no out of the box support for this. If you're using WPF you might be able to override the left mouse button down preview event, and if shift is pressed, set Handled=true on the event argument. That should prevent the mapview from doing anything with the event, and you can then do your own draw box code in the down/drag/up events.

‎09-08-2022

I don't know EF too well, but browsing their code it looks like it's just a wrapper around other spatial libraries, and there's some sort of provider that might give you access to the underlying sql geometry libraries.

‎09-08-2022

Hah glad it at least works now. > Yes when it fails to update to 100.15-preview4 it stays at 100.14.1-preview3 I generally don't trust the update dialog, but just change it manually in the csproj file.

‎09-08-2022

That project file is referencing 100.14.1 though?

‎09-08-2022

You're better off going through the geometry builders than going through WKT which would be extremely slow. Perhaps this code snippet here will help: https://github.com/dotMorten/GeometryConversions/blob/master/src/GeometryConversions.Shared/System.Spatial/SystemSpatialConverter.CreateGeography.cs

‎08-23-2022

Great! Glad it is working for you. Again thank you for making this easy to reproduce.

‎08-23-2022

What errors are you getting? Could you try and delete the \obj\ folder and restart Visual Studio?

Online Status	Offline
Date Last Visited	3 weeks ago

My Ideas

Latest Contributions by dotMorten_esri

Re: Loading a text symbol from a stylx file

Re: keep Polyline symbol same size when zooming out

Re: Supported platforms in MAUI

Re: Supported platforms in MAUI

Re: Keeping location pin on center of MapView

Re: LocationDataSource.LocationChanged not firing

Re: LocationDataSource.LocationChanged not firing

Re: Override out-of-box rectangle zoom

Re: Override out-of-box rectangle zoom

Re: Convert Polygon to DbGeography

Re: Update to 100.15.1 - preview4

Re: Update to 100.15.1 - preview4

Re: Convert Polygon to DbGeography

Re: WPF Per-monitor DPI awareness / Map goes missing

Re: Update to 100.15.1 - preview4

Re: NET 10 Support Maps SDK

Re: Could not build for iOS since upgrading to 200...

Re: MapView ignores first left-drag pan after righ...

Re: Level of Detail for Custom Tile Cache

Re: Level of Detail for Custom Tile Cache