LabVIEW
Labview 2015 strange error with type def. enum and case structure
@MaxEngee wrote:
Very interesting bug.
I created type def. from enum and connect it to case.
And the cases do not work properly.
If I disconnect from type def. all work correctly.
I agree with Matt -- it works "exactly as you told it to work". I notice you have a TypeDef, yet are creating two additional representations, a Numeric and a Message to represent the same thing, and maybe this is where you are getting confused.
Your TypeDef has three values: Get Settings, Get Data, and Close Subpanel. You might (logically) think they should be ordered that way, i.e. Get Settings would be (numerically) "first", and Close Subpanel would be "last". As you have defined your Enum, however, the order is backward, but so what? You can either ignore the numerics or change the order in the TypeDef by editing it and moving entries up and down as needed.
Here's a small variant on your "LabVIEW Error" VI that "takes advantage" of the backward ordering of your Enum and shows how to "step through" the values one at a time in a While loop, output the Enum Name (e.g. "Get Data"), the Enum Value (2, in the case of "Get Data"), and echo the value of the Enum itself by simply creating an Indicator ("Menu Ring") for it.
Note all of the "common code" takes place outside the Case Statement. I deliberately removed the "Default" value, which is not needed as all of the Enum possibilities are enumerated in the Case labels. This can help you prevent a bug if you add another "choice" to the Enum (e.g. "Process Data") -- once you change the Enum, your Case Statement will "break" until you add the newly-created Case to it. If you still had "Default" as a Case Label, when you said "Process Data", you'd repeat whatever Case was labelled "Default", probably not what you wanted.
Bob Schor
