LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
falkpl

update typedefs withoud enforcing strict runtime behavior

Status: New

I use typdefs for almost any data type I define in a program.  Most of the time I am concerned with the data only so a standard typdef is perfect.  sometimes I want to also have the look (properties) of the cluster or control stay the same throughout the code.  A strict typdef does this, but then causes problems like I cant change the properties at runtime.

I would like the ability to change the master typedef and update all instances to PROPERTY changes (ie size or color scheme...).  The current work-around is to temporary save the typdef as strict, close the typdef (causes the propertie changes to update) and then reopen the typdef make it a non-strict typdef and then save and close again.

 

There should be a synchronize option on typdefs.  Turn it on and the look of the typdef will be synchronized, turn it off and you have a standard typdef.

 

 

Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA
1 Comment
PJM_Labview
Active Participant

If you do a "File>>Apply changes" after changing the type, you don't have to close and reopen the typedef. This should save you a few extra steps.

 

But I like the idea anyway since I do that quite frequentlly.

 



  


vipm.io | jki.net