Please implement Short-Circuit evaluation for Blueprint

[JoeWintergreen]

@;713143

+1… Epic also killed off Kismet features that were far better & more powerful than Blueprints:
Question: Wouldn’t more control over wire layout mean using more Pure nodes and less Impure…
Surely the answer is yes in cases where Impure nodes get used to help simplify complex wiring…
So isn’t this issue also about excess space / the room BP takes up / screen-real-estate overall…

#1. Kismet vs Blueprints:
Straight line wires on any axis let you create more logical layouts, like with electronic circuits.
When used with collapsed Switch nodes for example, it meant neater layouts using less space.
Whereas curved BP wires means more screen space to avoid so many wires crossing & overlap.

#2. Kismet vs Blueprints:
Kismet let users drag PINS and re-order them on nodes, which also meant less crossed wires.
This had been requested before and was promised. So what happened, its an easy mod, no?

#3. Kismet vs Blueprints - UDK Shortcuts:
Minimize Sequence nodes. They take up too much space and add nothing to overall workflow.
Why not simplify them like it was in Kismet, so just connecting wires dragged off other nodes?
Delay option on every node (Exec pin) & Log/PrintString with multiple inputs, badly missed too!
Kismet also let users hide Node PINS not being used on a per-Node-basis not a global setting!

#4. Kismet vs Blueprints:
Kismet offered right-click deactivation of node branches. Afterwards ‘Exec’ wires turned red.
This had been requested before and was promised. So what happened, its an easy mod, no?

#5. Blueprint User Customization:
Anyone looking for user control of wire-color and layout styles along with node-style Vote here.
It would be helpful for example to have invoked Custom-Nodes look different from built-in Nodes.

          @Alexander_Paschall               @Sean_Flint

…yeah this all sounds great actually