Hi Martin (x2!),
the FormsEyeXHost class derives from EyeXHost, so when you use the FormsEyeXHost, then you already have access to all the EyeXHost functionality!
It’s perfectly fine to mix region-bound interactors (provided by the BehaviorMap) with global interactors (=data streams).
You can use as many BehaviorMaps as you wish as long as they don’t overlap (meaning that you cannot put the same control in two different BehaviorMaps).
The case with the two forms should be handled automatically by the framework. No need for pausing.
And yes, providing a UserControl with its own BehaviorMap is a good idea because it improves encapsulation. That’s how it’s done in the samples.