Latest Contributions by dotMorten_esri

Which platform are you targeting? (win32, uwp, ios, android or...). Wrt the exception, what is the message in that exception? The stack trace could also be helpful.

Are you also able to reproduce this with v100.14.0 ? Is it possible to make a small sample application with repro steps that demonstrates the problem?

I'm assuming - based on the forum this is asked in - that the user is using Runtime and not ArcGIS Pro. Unfortunately 'Clustering' is not yet a feature available in the runtime.

It appears Microsoft has fixed something in their certification process, and it'll now go through again. Could you retry submitting the app and report back if it also works for you?

Yes you are right - I should have caught that earlier. It is indeed taking the safe area into account on iOS (this is by design / on purpose btw)

Thanks for reporting this. A couple of question: 1. Are you able to see what message the Esri.ArcGISRuntime.ArcGISRuntimeException contains? (you might be able to catch it in an global unhandled exception handler) 2. Did the PC go into standby or screen saver mode during the time? This could potentially cause a GPU issue related to resuming rendering that might not be handled right (again the exception message would be helpful here)

Just following up after U14 shipped this week. Feel free to try this version and set the MaxExtent property on the Map. https://developers.arcgis.com/net/api-reference/api/netwin/Esri.ArcGISRuntime/Esri.ArcGISRuntime.Mapping.Map.MaxExtent.html

I'm looking at your screenshots and it appears to me that we can't actually see the bottom of the mapview, since the attribution area isn't visible. Is the mapview extending below those two bottom layouts you have? Also note the center isn't based on the middle between the bottom and the top, but between the top and the top of the attribution. If you do have the map being overlayed by other UI and want to take this into account for the center calculation, you can set the ViewInsets property to take this bit into account. For example: mapView.ViewInsets = new Thickness(0,0,0,height_of_overlay);

The template installer for WPF only comes with .NET 6 support and requires VS2022. This is because the We a few years ago removed the .NET Framework templates to be in line with the Microsoft recommendation to not use .NET Framework for new work. To use .NET Framework, instead create a blank WPF .NET Framework application and add the Esri.ArcGISRuntime.WPF NuGet package (this should even work in VS2017, although we don't officially support/test it). Just changing the framework in the SDK-style project isn't fully supported with .NET Framework. It's possible but might cause a few headaches (you could try adding <PlatformTarget>AnyCPU</PlatformTarget> to the PropertyGroup, and it might resolve this specific issue but I'd still recommend starting with the blank wpf templates instead)

Update 14 (out soon) will allow you to override the automatically set max extent initialized at startup.

Online Status	Offline
Date Last Visited	Tuesday

My Ideas

Latest Contributions by dotMorten_esri

Re: maps not working on .NET

Re: ArcGIS Runtime WPF application crashes when kept idle for sometime.

Re: Grouping nearby points

Re: Windows Store support in 100.13

Re: SetViewpointCenterAsync isn't actually in the center only on iOS

Re: ArcGIS Runtime WPF application crashes when kept idle for sometime.

Re: VTPK Setting maximum extent after switching basemap to portal item.

Re: SetViewpointCenterAsync isn't actually in the center only on iOS

Re: ArcGIS Runtime WPF App (.Net) with .Net 4.8

Re: VTPK Setting maximum extent after switching basemap to portal item.

Re: Documentation For Migrating From ArcGIS Engine

Re: Code to use MAUI (until official support in Ar...

Re: Current location heading issues after update t...

Re: "QueryTask" at 100.x

Re: Pan using middle mouse button