Latest Contributions by dotMorten_esri

Take a look at FeatureCollectionLayer / FeatureCollection for in-memory feature tables as well as just creating your own on on-disk Geodatabase using Geodatabase.Create and CreateTableAsync. This will allow you to store data in feature tables that you can render using a feature layer and apply cluster rendering to using the FeatureReduction property. Having said that, GraphicsOverlay also supports FeatureReduction. ... View more

I'm not entirely if you're saying the above log was with replacing with a new mapview on resume? If that's the case, could you try it with just leaving the mapview alone as in the original sample you shared? (it's fine that the map is blank - but I'd like to understand if something on your device is not triggering these lifecycle events, since the MapView heavily relies on these to resume rendering). I do find it curious so far that you are seeing destroy+create. That could be the root of how these devices behave differently. If you repeat this on a device that does work, do you see a version of mine or your log? Lastly what does "TextureView does some things" mean? ... View more

Thanks for confirming. You shouldn't have to re-create a new MapView. Just re-insert the same one. One more thing to also try. Could you try and add this to MainActivity? public class MainActivity : MauiAppCompatActivity { public MainActivity() { Lifecycle.AddObserver(new Observer()); } private class Observer : Java.Lang.Object, AndroidX.Lifecycle.IDefaultLifecycleObserver, AndroidX.Lifecycle.ILifecycleObserver { void IDefaultLifecycleObserver.OnCreate(ILifecycleOwner p0) => System.Diagnostics.Debug.WriteLine("***Lifecycle.OnCreate"); void IDefaultLifecycleObserver.OnDestroy(ILifecycleOwner p0) => System.Diagnostics.Debug.WriteLine("***Lifecycle.OnDestroy"); void IDefaultLifecycleObserver.OnPause(ILifecycleOwner p0) => System.Diagnostics.Debug.WriteLine("***Lifecycle.OnPause"); void IDefaultLifecycleObserver.OnResume(ILifecycleOwner p0) => System.Diagnostics.Debug.WriteLine("***Lifecycle.OnResume"); void IDefaultLifecycleObserver.OnStart(ILifecycleOwner p0) => System.Diagnostics.Debug.WriteLine("***Lifecycle.OnStart"); void IDefaultLifecycleObserver.OnStop(ILifecycleOwner p0) => System.Diagnostics.Debug.WriteLine("***Lifecycle.OnStop"); } } When I do this, this is what I see in the output window once the app comes back from the sharing operation. I'd be curious if that differs on your Samsung device: [TextureView] Paused by user [TextureView] Stopping pulse [0:] ***Lifecycle.OnPause [0:] ***Lifecycle.OnStop [0:] ***Lifecycle.OnStart [0:] ***Lifecycle.OnResume [TextureView] Resumed by user. Texture view available: True [TextureView] Starting pulse   ... View more

Thank you for sharing the log. I do see the rendering stops for the mapview on share (which is expected), but I don't see a resume. As an experiment could you after sharing, try and remove the mapview from the view and re-insert it? Would that make it start up again? That would confirm if we're having some issues detecting resume. ... View more

Do you _only_ see the issue on this device, or is it the only device you've been testing on? (what devices do you have that it worked on?) Does LogCat give any indication of an issue with the application? ... View more

Rasters will rotate based on their world file or georeference coordinates. If you rotated the image, it wouldn't align with the underlying map any longer. If you generate these images, can't you generate them in an un-rotated fashion? (as in north up). ... View more

If I'm not mistaken, Legend isn't supported for a DictionaryRenderer. Try calling _myFeatureLayer.GetLegendInfosAsync() and see if it returns anything. ... View more

I'm curious: Does it work if you instead of using *, add all the missing field names to the list? I'm curious if it's a bug wrt using *, or if the data just isn't being made available for whatever reason. ... View more

Also make sure you target `net8.0-windows10.0.19041` or higher with the explicit windows version in the target framework. A new WPF project typically just specifies `net8.0-windows` which is equivalent to Windows 7. We require at least `10.0.19041`. Btw you don't need to install `ArcGIS_Maps_SDK_DotNet_200_7_0.vsix`. That just gives you a local nuget repo of the packages (for offline scenarios), but they are on nuget.org so they'll just pull from there instead. ... View more

Since we haven't been able to reproduce, there hasn't been any progress. If you have a reproducer you can share, I'll be more than happy to take a look. ... View more

The default callout, no, but you can instead use the overload that takes a UI Element, and put whatever user-control you want inside it: https://developers.arcgis.com/net/api-reference/api/netwin/wpf/Esri.ArcGISRuntime.UI.Controls.GeoView.ShowCalloutAt.html#Esri_ArcGISRuntime_UI_Controls_GeoView_ShowCalloutAt_Esri_ArcGISRuntime_Geometry_MapPoint_System_Windows_UIElement_System_Windows_Point_ ... View more

No the anchor is only to a certain location, and not scaling. >  Is this a feasible plan, given we will have a few hundreds of devices on the map as graphic overlay ?   This will definitely give you performance issues. The feature is meant for minor set of elements like callout to be placed at a location. For high performance rendering you really need to be rendering with the existing layer types - XAML just isn't geared for that kind of dynamic rendering. You could look into the raster layers which allows you to place raster images that'll scale with the zoom. ... View more