Execute Sequence disregards ON/OFF states of Children
-
@Aidan-Oxley You could use a behaviour bundle one down from the first behaviour dropped down from your sequence to make this happen. Switch off the behaviour bundle. The behaviour above it (could be a comment) takes that cycle's slot/call.
-
@Deeeds I like the idea of a switch for this now. But I definitely do not want it to skip past turned off behaviours by default without a switch.
-
@Aidan-Oxley Since you're addicted, yes a switch.
But it should have been skipping OFF behaviours as a default. This is another area that caused much head scratching and figuring to find what was causing odd behaviour by the behaviours in the behaviours editor.
By which I mean to say, it's time they were called nodes, and "behaviour" (the word) be reserved for things that determine/create or actually are... behaviours.
-
@Deeeds That’s up to hyperPad team what they decide to name them. I don’t think it matters that much, I’ve never seen anyone complain about behaviour names before you (well there were a lot of things no one complained about before you 😜).
-
@Aidan-Oxley by the looks of things, I'm the only tool using it as a tool.
-
@Deeeds Using hyperPad as a tool? You’re trying to tell me you’re the only one using hyperPad? Or do you just mean using it professionally?
-
@Aidan-Oxley There is a logical AND involved.
I'm the only TOOL, using hyperPad as a TOOL.
-
@Deeeds I don’t get it 😐. HyperPad is a tool, you’re a tool too? Idk what that means.
-
@Aidan-Oxley 46 & 2
It's one of the few bits of math I know.
-
@Aidan-Oxley said in Execute Sequence disregards ON/OFF states of Children:
@Deeeds I don’t get it 😐. HyperPad is a tool, you’re a tool too? Idk what that means.
Yes, he’s a tool. You could think of him as a sledgehammer(nice tool, right?).....
Hard head, rather blunt, smashes things, and is top heavy. -
I’m going to agree with @Aidan-Oxley, a switch would be best.
-
@iTap-Development hahahahhaha
-
@Deeeds Tool is awesome.
