Lost typedef-ness

[Ken_Brooks]

I created a complex cluster control. I said "Make typedef". It did, and I saved it as Meta Bundle.ctl . I created several instances of it, in various VI's. But now, if I right-click on one of them, the menu item says "make typedef" not "open typedef". And if I drag from the control from the project window (or from its icon in the upper right of its own window) into another VI, the created instance likewise says "make typedef" not "open typedef". This happened to more than one custom control. It seems like they're losing access to their typedef nature.

Is this a familiar problem? Any help for it?

[paul_cardinale]

Never saw that before.

Post Meta Bundle.ctl and I'll look at it,

[billko]

Be careful that you are actually dragging the control either from the project or from the icon of your open typdef.  A common mistake is to drag the actual control off the front panel of your .ctl file onto wherever you want it to be.  This will NOT create a typedef'd link.

[crossrulz]

---

@Ken_Brooks wrote:

I created a complex cluster control. I said "Make typedef". It did, and I saved it as Meta Bundle.ctl . I created several instances of it, in various VI's. But now, if I right-click on one of them, the menu item says "make typedef" not "open typedef". And if I drag from the control from the project window (or from its icon in the upper right of its own window) into another VI, the created instance likewise says "make typedef" not "open typedef". This happened to more than one custom control. It seems like they're losing access to their typedef nature.

Is this a familiar problem? Any help for it?

---

That sounds like you saved the ctl as a "Control", not a "TypeDef".

[Ken_Brooks]

Crossrulz, where would I even make that choice?  I've always saved my new typedef controls without giving it any thought!

[Ken_Brooks]

Here is the weird control, slightly renamed to make room for my newer attempt.

[paul_cardinale]

You've saved it as a Control, not as a TypeDef.