Latest Contributions by dotMorten_esri

Change the unit test project targetframework from "net7.0" to "net7.0-windows10.0.19041.0".  ... View more

When you say zooming, do you really mean "move forward" ? Traditional zooming can be done by setting the field of view on the SceneView, which matches what a zoom-lens would do (ie not moving forward, but merely reducing the FoV): https://developers.arcgis.com/net/api-reference/api/netwin/wpf/Esri.ArcGISRuntime.UI.Controls.SceneView.FieldOfView.html Otherwise if you want to manipulate the location of the camera, grab the Camera property on the SceneView to get the current Camera, and then use all the properties (like MoveForward) to modify the camera. See the full list here: https://developers.arcgis.com/net/api-reference/api/netwin/Esri.ArcGISRuntime/Esri.ArcGISRuntime.Mapping.Camera.html#methods Once you got the new camera you need, you can use SetViewpointCamera/SetViewpointCameraAsync to apply the new camera: https://developers.arcgis.com/net/api-reference/api/netwin/wpf/Esri.ArcGISRuntime.UI.Controls.SceneView.SetViewpointCameraAsync.html If you want to stay fixed on a specific location or geoelement, also take a look at the various orbit camera controllers: https://developers.arcgis.com/net/api-reference/api/netwin/Esri.ArcGISRuntime/Esri.ArcGISRuntime.UI.CameraController.html https://developers.arcgis.com/net/api-reference/api/netwin/Esri.ArcGISRuntime/Esri.ArcGISRuntime.UI.OrbitGeoElementCameraController.html https://developers.arcgis.com/net/api-reference/api/netwin/Esri.ArcGISRuntime/Esri.ArcGISRuntime.UI.OrbitLocationCameraController.html https://developers.arcgis.com/net/api-reference/api/netwin/wpf/Esri.ArcGISRuntime.UI.Controls.SceneView.CameraController.html   For a more advanced example, here's a way to control the camera using a game controller: https://github.com/Esri/arcgis-maps-sdk-dotnet-demos/blob/main/src/KmlViewer/XInputHelper/XInputSceneController.cs ... View more

I trust the testing the team-members do. In addition it is backed up by numerous layout fixes in the .NET MAUI previews. ... View more

> So whats the plan here? Since this is a layout bug outside the Maps SDK, you have a few choices: Work around it (as mentioned above it fixes itself quite easily by not relying on auto-sizing or rearranging layout layered instead of gridded. Wait for .NET 8 to ship with the fix (and/or use the preview for now). Push Microsoft to backport the fix to .NET 7. ... View more

Could you share some examples of what you see, and what you expect? Also could be helpful if you can share the symbol definition (for instance use symbol.ToJson), or even better share a sample that demonstrates the problem. ... View more

You can use your own internal basemaps - it's only the pre-defined arcgis online basemaps (ie the ones that use the BasemapStyle) which require an API Key ... View more

Sorry for the slow follow-up. I've been spending some time debugging this, and I'm 99.9% sure this is a layout bug in .NET MAUI, and not in the ArcGIS Maps SDK. It's sending some weird layout parameters when you use the specific configuration you have above, causing the map to size itself to 0. However I did find numerous other ways to get the layout you want without triggering this bug, so you should be able to move forward. ... View more

There is no out-of-the-box setting for disabling individual gestures. However one approach is to override the mapview template. If you in the WPF designer right-click the mapview and select "Edit Template -> Edit a Copy" you'll get access to the XAML control template. In the template find the Rectangle that's called "ZoomBox" and delete it. ... View more

You could use the select feature to highlight it - I do believe that also brings it up to ensure the highlight is visible. Of course that implies getting the feature highlighted as well, which you may or may not be interested in, but it would ensure the user can see the data. ... View more

You can do that, but it will _have_ to be two separate builds, or your class library _must_ target 100.5 (and only use 100.5 APIs), and a 100.15 _app_ can reference that library. If you want to access 100.15 APIs in your class library, you must reference 100.15, but that would mean any app trying to use that library must reference 100.15+ as well.  ... View more

You can use preprocessor constants to do this. In a project's csproj you'd add a new constant to a PropertyGroup: <DefineConstants>$(DefineConstants);ARCGISRUNTIME_100_15</DefineConstants> Then in code you can do    #if ARCGISRUNTIME_100_15 labelInfo.ArcadeExpression = $"$feature.{expression}"; #else labelInfo.TextExpression = $"[{expression}]"; #endif   However you won't be able to compile it into one class library and reuse it, since you can't make this check at runtime. So you'd have to use a shared project or linked file into the project that references the constant. You'd have to reference 100.15 to write code that access both the new and old properties, but that means a 100.5 project won't be able to reference that project, since it is built with a newer library. ... View more

I've been able to reproduce this, and while I don't have a fix/explanation  right at this moment, I was able to get the behavior you're looking for with a slightly different layout: <Grid> <esriUI:MapView x:Name="MyMapView" /> <Grid ColumnDefinitions="*, Auto" RowDefinitions="*, Auto"> <Button Grid.Row="1" Grid.Column="1" Text="..." /> </Grid> </Grid> ... View more

Sure but historically there's never been envelope as a geometry type in the geodata. The envelope is a special case geometry mostly used to just determine extents of a geometry and as such is a "helper" type separate from the other types. In hindsight it probably shouldn't have inherited from Geometry to begin with. ... View more