Disable Structure

[ouadji]

                                              With only 2 subdiagram, the Disable structure should behave in all cases like a flip-flop.

                                                                                        it's not currently the case and it's annoying

[SteenSchmidt]

@Intaris: Seriously, maybe that's a better suggestion, to remove the "Disable" option of the Disable structure? Adding functionality by removing features. That's lean 🙂

/Steen

[ouadji]

"the "Disable this case" option should simply be removed"

YES !!!!

      

Adding functionality by removing features.

It was simply a bad feature. (I'm serious)

[ouadji]

Adding functionality by removing features. That's lean

no, it's brave and courageous !  

(sorry for my bad english, i do my best    )

[altenbach]

There is nothing wrong with forcing the user to go to the desired case before enabling it. Here, all other cases will be automatically disabled and we can look at the new enabled case for visual confirmation that it is the one we actually want. It is a bad idea to automatically enable another case (that we currently don't even see!). No kudos.

I do I think it is incorrect that the VI breaks if all cases are disabled. Code with all cases of a diagram disable structure disabled should be perfectly legal and should not break the VI. This might be a new idea though. This old idea comes close.

[ouadji]

@altenbach:

Code with all cases of a diagram disable structure disabled should be perfectly legal and should not break the VI.

I totally agree, it is a good idea.

that's also a good way to solve the problem.

[Intaris]

I'm unsure about allowing a structure with outputs to not break code if all cases are disabled.  That seems weird.

[ouadji]

for me, the real solution is : remove the option "Disable this SubDiagram" ....

but the proposal of altenbach seemed to me to be a good alternative. (the least worst)

[Manzolli]

@Intaris "It still seems like a weird solution to a problem which is essentially that the "Disable this case" option should simply be removed."

Agree! Simple, direct and focus on the positive side. Kudos for you!

[altenbach]

I'm unsure about allowing a structure with outputs to not break code if all cases are disabled.  That seems weird.

As long as all outputs have a defined datatype (and they do!), the behavior is not really different to the current case where we have an empty, but enabled case just sitting there doing nothing. Since it has no code by default, why even show it as if there is more to it than meets the eye? The compiler can still maintain tha extra empty case under the hood, but it should not bother the programmer with it. 😉

[GregFreeman]

Good call Shane. Make an idea, I'd vote.