LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

strict type def. ring bug?

I just noticed that the strict type def. of a ring is not updated as i would expect.
I put one instance in front panel and one as a constant in block diagram. If i change the strict type def. only the front panel control is changed.
Shouldn't the block diagram constant be updated too?
(Auto update is on)
0 Kudos
Message 1 of 6
(3,650 Views)

You are not alone in your expectations but no that is not a bug, see here.

Unlike the enum data type the strings of a ring are NOT part of the data type and therefore changes to the typedef DO NOT update all instances.

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 2 of 6
(3,638 Views)

Labview needs one additional type between strict type def and a normal typdef, one which will update the look of all references when the typdef is changed but not strictly enforce the type.  I have this issue often where strict types (like a ring) is unusable (because of the inability to update certain properties like strings[]) but keeping a common look throughout an application.  The only work around for these situations are to update the look of a control typdef, save the typdef as strict, close the typdef, reopen the typdef set it from strict back to a regular typdef then continue programming as usual.  A lot of extra steps just to keep interface consistency. 

 

Paul

Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA
0 Kudos
Message 3 of 6
(3,635 Views)

Thanks guys...

I think NI should change a little, the way a Ring works.

0 Kudos
Message 4 of 6
(3,618 Views)

Place this .llb in  ...\National Instruments\LabVIEW xxxx\project\
The next time you run LV, it will show up in the Tools menu.
When you run it, it shows a list of all Ring TypDefs in memory.  You select one, then click OK, and it updates the strings & values all instances of that TypDef that are in memory.

0 Kudos
Message 5 of 6
(3,079 Views)

I found a much simpler way to code it.  Here's the new version.

0 Kudos
Message 6 of 6
(3,055 Views)