Activation and RoutedViewHost don't play nicely together

[jen20]

RoutedViewHost being derived from TransitioningContentControl means that whenever you navigate to a new view model, the old one is reactivated as it is loaded again when it becomes the "previous" content in the TransitioningContentControl (at least I think that's what I'm seeing!)

If that's the case, it might be an idea to have a NonTransitioningRoutedViewHost as well (or ideally to have RoutedViewHost deriving from ContentControl and TransitioningRoutedViewHost deriving from TransitioningContentControl, thought that might be a breaking change too far).

I'd be happy to look into this, I have a version implemented in my project at the moment (which is for a fixed screen size so nixes the orientation stuff which makes it otherwise impossible to implement outside of the ReactiveUI assembly because of the internal IPlatformOperations).

Any thoughts?

[anaisbetts]

Let's just fix the bug :) I think we can do something like combine Activated and HitTestVisible to make this work

[jen20]

True that would also work ;-) will take a look.

[jen20]

Actually irrespective of this, non-transitioning versions of these are useful for if you have annoying controls like WebBrowser which have airspace issues with TransitioningContentControl.

[anaisbetts]

@jen20 I think you can just override the template, yes?

[jen20]

That's probably a better solution.