One idea which could solve problem #1 would be to add a method IFlowComposer.replaceController() which would dispatch an event with the old controller and the new one.
But, this doe not solve problem #2. There must be some way of solving this using composition… On May 27, 2015, at 1:18 PM, Harbs <harbs.li...@gmail.com> wrote: > When loading Squiggly, it modifies the controllers in the FlowComposer and > swaps out the existing controllers with SquigglyCustomContainerControllers. > > This is problematic: > 1) There’s no way to track ContainerControllers while using Squiggly. Any > tracked ContainerControllers become unused. (I currently have this problem. I > have some code which tracks threading across containers.) > 2) If someone subclasses ContainerController for some reason, their code > blows up. > > Any suggestions on how to solve this problem? > > Harbs
