do not update non-strict typedefs

[Alexander_Sobolev]

If you change the non-strict typedef, it resets visual appearance of all instances to new state. Is it a bug, or a feature?

IDEA - it should not be so!

I thought, that _basic_ difference between strict and non strict typedefs is that all instances of the strict ones (and ONLY they) have the same appearance. 

Examples:

Clusters of parameters, displayed to the user and used in SubVIs. User instance is painted, custom designed. You add new parameter - bang, design of all others vanishes. In subVIs controls and indicators should have standard design - customized elements are not desirable.

Clusters in block diagram constants: visible labels, vertically (or horizontally) aligned elements, sized to contents. - everything will be lost.

Similar ideas

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Allow-Strict-Type-Def-of-Type-Def/idc-p/1135856#M5700

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Independence-from-Strict-Type-Definition-without-Repre...

[smercurio_fc]

I'm a little confused. What are you proposing that's different from those other ideas?

[Alexander_Sobolev]

There are several differences, 

1) My idea is more low level - does not require additional programming (or changing programming steps)

2) Other ideas propose to fix the appearance of the control manually - set a basic typedef, defining type. Then make new files (or inside the same file), define several visual designs. But what will happen with these strict typedefs, when you change the basic control (add new element to the cluster)? In present LabVIEW behavior (without my idea) they will reset to default state.

3) Block diagram appearance: I place the typedef cluster on block diagram and arrange elements horizontally (or vertically), and it seems logical not to reset this setting, when adding new elements to the cluster.

[Darren]

Any idea that has received less than 2 kudos within 2 years after posting will be automatically declined.