ConductResult from CMContrib - closing Screen does not work correctly

Topics: Actions & Coroutines, Extensibility, Framework Services
Mar 16, 2013 at 11:41 PM
Edited Mar 17, 2013 at 12:02 AM
I'm using CM.Contrib library, specifically I'm using ConductResult, which shows (or conducts an item) in specified Conductor:

It provides a neat extension methods for executing coroutine after/before closing/activating given item.

However, I have an issue. After I issue closing a child (which is Screen) in that specific child using TryClose(), I'm called back using ConductResult, then I want to show a different child (again Screen).

The issue is that, first is the new child activated in parent conductor, but after that a null item is activated! Which is totally wrong behavior, for me.

ConductResult (see link above) uses regular Deactivated event from IDeactivate interface, checking WasClosed field from DeactivationEventArgs class.

Edit: basically, I need to open childB, after childA is closed in parent conductor. What is the cleanest way to do this (preferably with coroutines and without overriding default behavior of Conductor)?