Else If behaviour child behaviours don’t follow when moved

[Kamdroid]

When moving a behaviour which contains an else if statement, everything under the else if statement doesn’t move with the rest of behaviours as expected

[Deeeds]

@Kamdroid Yes, seen this...

And those funky lines. I want curves. Sexy, sexy curves. Like this:

[Aidan_Fire]

@Deeeds Did you know that GamePress used to have curves, not corners? 😛 I really don’t like Else Ifs, I never ever use them because they are unnecessary and they cause some problems like @Kamdroid said.

[Deeeds]

@Aidan-Oxley How do you avoid elses ?

[Deeeds]

@Aidan-Oxley said in Else If behaviour child behaviours don’t follow when moved:

Did you know that GamePress used to have curves, not corners?

why did they leave?

[iTap Development]

@Deeeds said in Else If behaviour child behaviours don’t follow when moved:

why did they leave?

Because the devs removed them!

@Aidan-Oxley i couldn’t live without else ifs.

[Aidan_Fire]

@Deeeds I just use more Ifs, if x = a and if x ≠ a etc. Don’t ask me why the curvy lines left, I guess they decided to change their style or something.

[Deeeds]

@Aidan-Oxley It's an odd choice. These square lines are both ugly and hard to "read" when they overlap and interact.

[Murtaza]

The if/Else is visually broken. We thought we were so cool when we came up with that design concept. Boy did we immediately regret that.

We'll be changing if/else so they are a single behaviour with 2 sets of outputs.
Left side is the IF, right side is the else.

As for curved lines, when we rewrote hyperPad, the lines were removed for performance reasons. The way the lines are being done are actual a performance hit. The beahviour screen is actually a cocos2D scene. We noticed users were getting more and more complex with their behaviours so we ultimately removed the curved lines. I'd like to see them back one day. I do love some bezier curves.

[Deeeds]

@Murtaza said in Else If behaviour child behaviours don’t follow when moved:

We'll be changing if/else so they are a single behaviour with 2 sets of outputs.
Left side is the IF, right side is the else.

May I be so bold as to make a suggestion?

Oh. You can't wait?

Here it be:

Bottom Out is If = true, right side is Else.

Keep the left side of Behaviour nodes reserved for inputs (eventually), and the flow going down and to the right.