Nasty LV Quirk

[pincpanter]

The property node does not disappear if the TypeDef is first promoted to Strict, then downgraded to Control.

Of course, the container vi must be in memory and changes must be applied for each modification.

[wiebe@CARYA]

---

@billko wrote:

How about finding each instance and disconnecting it?  Then, only after all the typedefs have been disconnected, make the typdef a control?

---

If all instances are disconnected, you might as well delete the type def...

[paul_cardinale]

I've hit a bump in the road with my scripting: In addition to disconnecting the boolean controls, I want to disconnect any linked boolean constants; but I can't figure out how to get the typedef path from a boolean constant.

[wiebe@CARYA]

Use the type def path property?

Or get the constant Terminal value (variant), and use variant tools to get the type def path:

[billko]

---

wiebe@CARYA wrote:

---

@billko wrote:

How about finding each instance and disconnecting it?  Then, only after all the typedefs have been disconnected, make the typdef a control?

---

If all instances are disconnected, you might as well delete the type def...

---

Well, he did say he wanted to keep the control as a control.  The whole point was to make it a control without making all the property nodes go away.