Scripting: Insert Case Structure Frame

[10Things_Rob]

Working in LV2020...

I have the following scripting code in order to insert a new frame into a case structure.

It works great... except LabVIEW doesn't realize it.

The target VI is broken with the following error: 

Thing is, it's there. Correct selector value and everything.

If I edit the case selector by adding a space and then deleting it, the VI fixes itself.

If I add one, then a second, then delete the second one, then the VI fixes itself

(so clearly nothing is actually WRONG with the first one I created)

Any Ideas what's going on?

NOTE: I did used to have Begin/Add Undo Transaction but the "dirty dot" never appeared, and I've been trying to simplify it down to the absolute minimum number of functions.

NOTE: The VI (or Block Diagram) being open and visible does not affect the behavior.

[raphschru · Accepted solution]

Hi,

It seems like a bug of CaseStructure property "FrameNames" that does not properly recompile the VI.

Try forcing recompilation with VI method "Compile":

I managed to reproduce a similar behavior, but not exactly what you described.

Please attach code or at least provide more details on the selector data type (boolean, integer, enum ?) and the exact values written to "FrameNames".

Regards,

Raphaël.

[wiebe@CARYA]

Those frame names are tricky.

If the case uses strings, you might need to quote the string, like the case structure does when you type a string.

For enums, you shouldn't quote the strings, as the case structure doesn't do that when you type the enum names...

It's quite crude. It would be nice to have functions that return actual data in stead of literal strings.

Not sure if that's what's going on. So code would indeed help.

[paul_a_cardinale]

Here is what I find:

Note that there are always leading and trailing spaces.

[10Things_Rob]

Wiebe (and future readers),

At your recommendation, I tried adding quotes and even adding spaces before/after quotes.

Neither worked (at least in 2020)

The VI Compile solution did seem to work though.

Thanks for your input.

-- Rob

[10Things_Rob]

Here's the testbench I was using to experiment.

The compile seems to do the trick.

I have not tried this on any version other than 2020.

__PRESENT

[raphschru]

---

@10Things_Rob wrote:

Here's the testbench I was using to experiment.

The compile seems to do the trick.

I have not tried this on any version other than 2020.

__PRESENT

---

I have tried with LV2024 Q3 64bit and the issue is still there.

Since you've most likely found a bug and a way to reproduce it, I would suggest to report it to NI.

You can simply give them a link to this forum thread so that you don't need to repeat all the steps to reproduce the bug.

Regards,

Raphaël.

[10Things_Rob]

Done. Thanks.

__PRESENT

[raphschru]

The bug is still present in LV2025 Q3,

@10Things_Rob did you by any chance get a bug number when you reported it to NI? If yes, could you post it here?

[sckLV]

I had some very similar scripting code (nearly identical) and it used to work on LV2025Q1, maybe even 24Q3. Well, it stopped working around the time I installed 25Q3. I fixed my code by duplicating the new case and then deleting the duplicate. I think this is similar to recompiling the BD.