UrhoSharp on UWP Xamarin Forms - Disposes when you Navigate to new Page

[najak3d]

ISSUE: Urho App Disposes when you Navigate to a new Xamarin Forms Page.

Xamarin Forms apps are composed of Pages. If you navigate to a new page, the current page which hosts UrhoSharp View, will cause the Urho App to "StopRunning" and gets disposed. When you navigate back to this page, you have to reconstruct your whole UrhoApp from scratch! This causes lag and memory thrashing.

We wan the UrhoApp not only to Not-Dispose, but want it to keep running, such that we can use it to Render outputs to the pop-up forms.

Our app is a Map app with trip planning.

1. The base page is a full-screen map, rendered by UrhoSharp.
2. You can then go to a Trip Planning page, that ALSO renders the map, but in a way that is associated with your trip planning UI.

So we'd like to be able to either:

1. Rebind Urho to the new page. OR
2. Have UrhoSharp run headless, so that we can control when it Disposes() of the App, instead of having page Navigation uncontrollably stop Urho from running each time you go to a new page.

====
WE ARE WILLING TO DO THIS WORK. But as of now, we cannot figure out how to get the UrhoSharp project to build. Getting it to build is a huge hurdle here, as the published instructions seem to be flawed or lacking. We need some hand-holding and then can get this built.

ALSO: We're not sure if this same defect exists for Android/IOS - but if it does, we'll need this fix to be applied to UWP, Android and iOS alike.

====
This defect makes UrhoSharp non-usable for us in a multi-page Xamarin Forms app.