FWIW, I solved my specific issue by using an index instead of a reference to
the controller, and I always resolve the controller using
flowComposer.getControllerAt(_flowIndex);
As for the why:
Squiggly replaces the standard ContainerController with a
SquigglyCustomContainerController (which ext
I haven’t looked at the code at all, but maybe it would be worth trying to
figure out “why” Squiggly replaces the controller. I would imagine it is
to get certain events so it knows when to run its spell checker and/or
injecting the squiggly decoration. Having the controller dispatch the
right ev
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, Har
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 cur
