Why aren’t the outputs of bricks nested within a Control Flow Brick available outside the Control Flow brick?

PixieBrix Control Flow bricks are implemented similar to closures in popular programming languages like Javascript.

By β€œfreezing” the environment passed into a branch/body of a Control Flow brick and preventing it from modifying the available Output Keys outside of the brick, the behavior of bricks are more predictable (to PixieBrix’s debugger and humans!). Predictability allows use cases like button handlers and rendering sub-panel elements in parallel

Last updated