I find the current behavior to be counter intuitve. Kudo!
>
"There is a God shaped vacuum in the heart of every man which cannot be filled by any created thing, but only by God, the Creator, made known through Jesus." - Blaise Pascal
How about being able to NAME the disable frames and when hovering over the selector, we have an auto pop-up whereby clicking on a case will activate it.
I for one would LOVE to have at least names for my individual cases because it usually involved benchmarking....
Actually, removing the default case does not necessarily break a VI. A case structure that is only True or False does not have a default case. A case structure driven by an enum does not need a default case if there is a case for every item in the enum.
@RavensFan: True for Enum, but not true for True/False Case Structure because it never had one “Default”, so you cannot remove it. But the point I want to make, it is still true, in any case: always should be a visible code to be executed. “Default” is necessary when there is a possibility of none of cases be an answer to the data connected to the Selector Terminal, covering any other case not created (coded).
How is what I said not true?
I said the True/False does not have a default case. I never said anything about whether True/False EVER or NEVER had a false case. Yes, you're right, True/False has never had a default case. Which still proves my point.
Out of curiosity, I made a True/False case structure and tried to type in Default for one of the cases. It did not take it. I also tried deleting one of the cases. It broke the VI because it did not have a case for every possible value. That is correct behavior. So I tried typing in Default for that lone case that remained, (So a single False, Default case, should be acceptable since a True would still cause that case to run by default since there is no true case separately defined.) It still did not take the word default, and the VI remained broken. It was interesting because it was somewhat different behavior from working with an Enum selector. But not really a problem because who in the real world would want a True/False case structure and eliminate a case or have a "Default" case?
By the way, I like Intaris's idea of being able to name the cases in the disable structure. It gives you the possibility have identifying the different scenarios that you may be trying out among multiple Disabled cases. But I don't think it is necessary. I would just as likely drop a comment into the respective cases, or use the new subdiagram label to give each case a title.
@RavensFan: don't need to shout, it's not polite. I'm not a native English speaker, please forgive some mistakes I do. By the way, there are many people all over the world in the same situation as me, trying to help improve LabVIEW.
Even though you are right, the focus should be the idea being proposed. I think it always should be an executable visible case (even empty) in the Diagram Disable Structure. This always happens in the Case Structure, with or without “Default”.
Bottom line: we want a language to be logic and clever. Smart enough to understand and deal with some programer's craziness, but no allow things that are useless or not logic.
@Intaris: I also liked the idea of naming the cases in the Diagram Disable Structure. Where I kudo it?
@RavensFan: “Why do you say I shouted?”. Please check this All caps
For modern computers (after Internet become open to everybody) to emphasize something you can use the language (adjectives) or bold. Capital letter may considered “"shouting" or irritating”. By the way, the first computer I worked on was an ZX81, mentioned in the Wikipedia's article.
I apologize if looked like I was trying to correct you. Probably in a bad way I was trying to say was: it is no good having no code (even hidden an empty case) being executed. I was trying to use the Case Structure as an example. The possibility of remove the Default in some cases was not important. Argue about this is waste of time.
It was only 2 words in the middle of a sentence which I was trying to emphasize. I don't consider that shouting. A whole sentence, or a whole message. Then that would be shouting.
The link you posted even says that as well.
Quote:
While all caps can be used as an alternative to rich-text "bolding" for a single word or phrase, to express emphasis, repeated use of all caps can be considered "shouting" or irritating.
