Latest Contributions by dotMorten_esri

Have you thought about parallelizing your projections? Also try and reuse/cache whatever you can, like get a reference to a spatial reference, and reuse it. There's also been some big improvements, especially around how spatial references are handled, which in some cases speed up somethings up to 400x ... View more

Could you place a second graphic with a TextSymbol next to the circle? You could set the graphic location to just be the top of the extent of the circle, and middle of the sides. ... View more

That's more of a Xamarin.Forms specific question. Did you try something like what was mentioned here? https://forums.xamarin.com/discussion/27323/how-can-i-recognize-long-press-gesture-in-xamarin-forms  or https://alexdunn.org/2017/12/27/xamarin-tip-xamarin-forms-long-press-effect/  ... View more

Any chance you could share a simple application that reproduces the issue? As a workaround you could try and enable a legacy-mode that disables the secondary UI thread (just note it could potentially have a small performance impact) : AppContext.SetSwitch("Switch.Esri.ArcGISRuntime.DisableSecondaryUIThread", true); Note: You'll need to use v100.7 for this switch to work (if you can't move to 100.7, at least just try it briefly just to confirm whether this is the addresses the issue, so it gives us something more to go on wrt trouble-shooting). Also this switch might or might not continue to have an effect in future releases, so providing a reproducer sample would be helpful so we can try and address any issue there might be here. ... View more

You wouldn't see an error until you try and load the KML Dataset. Ie await kmlLayer.Dataset.LoadAsync(); ... View more

D'oh! Can't believe I didn't spot this. You're calling async code from C++, and that doesn't go well. Try chancing the async calls to use .Result instead to make them synchronous: bool b = MobileMapPackage.IsDirectReadSupportedAsync(m_PackageFileName).Result; Then you hit the catch code and you can see a proper error message. HOWEVER don't use .Result (or .Wait()) in production as it can create lots of dead-locks if your app is multi-threaded. You should probably switch do some sort of callback/eventing model instead. ... View more

>  I really think it you ran the app I attached and stepped though the code you’d get a better idea about what’s going on. I did and identified why the load operation wasn't working (assemblies not loaded). Now that we addressed that, I can't step further because I fail (correctly) on missing the MMPK, but since that was expected behavior when I don't have that file, I can only assume something else is going on with the file itself. Make sure you enable mixed debugging (both native and managed), and monitor the output window for any hints as well. ... View more

If initialize succeeds and you see the assemblies load, that isn't the issue any longer. What exception is .NET throwing in this case? Also does it work if you do a "normal" .NET application and execute the same code? ... View more

...here's the error I get if I call Initialize() in your reproducer: Error initializing ArcGISRuntimeEnvironment. Unable to find ArcGISRuntime deployment folder. Ensure there is a folder named "arcgisruntime100.6" in the same folder as your application executable, or set ArcGISRuntimeEnvironment.InstallPath to reference an alternative location. The deployment folder must contain sub-folders matching the process architecture of your application. Then I realize it's not even deploying the native files. The quick fix is to migrate away from Packages.config: Once you do that, your app should run just fine. ... View more

Also calling ArcGISRuntimeEnvironment.Initialize() at app startup should give you a much better error. When deploying the plugin make sure the native resources (ie the ArcGISRuntime100.x folder) is located next to the executable (ie not next to the Esri.ArcGISRuntime.dll assembly). Otherwise use the InstallPath Mike is proposing. ... View more

For zoom-out you'd have to calculate the 'opposite' rectangle, which granted isn't straight-forward. Typically you'd expand around a location inside the rectangle by a certain amount relative to the size of the rectangle (a smaller rectangle would typically mean zoom out more). It's a bit of math, but not horrible, so play with a few values and see what works for you. The simplest would be just to take the current map-scale, and multiple it by the relative width between the view size and the rectangle size, and then zoom to that. ... View more

If you want to use based on a rectangle, convert the rectangle to an Envelope in map units ( MapView.LocationToScreen(...) ), and use the SetViewpointGeometryAsync(Envelope). You could also use the sketch editor to draw that rectangle, and then just pass it straight to the setviewpoint method ... View more

Could you describe a little more what the scenario is that you need this for? How would you expect this to look like, and when should it fire? ... View more