Quote:
Originally Posted by capink
I dismissed the idea because it can cause problems like circular dependency. You can prevent a chain from directly calling itself, but it can do so indirectly through another chain that might reference it, and this would require a complicated dependency checking before running chains. You can write these action(s) for yourself as custom actions if you want this be a generalized solution, but I think it is opening a can of worms.
|
- Start ActionChain#1
- It calls ActionChain#2
- But then that calls ActionChain#1
- Which again calls ActionChain#2
- And once again, it calls ActionChain#1...
I don't think there's any good way to halt a chain in progress, is there?
