Control stops being a typedef

[PaulG.]

I create a typedef. I'll place it as a constant on my BD. After coding for a while I'll go back to it to modify it. When I right-click on it it fails to give me the "open typedef" option. As a workaround I delete it then replace it with the one on file and it works fine and I can open it as a typedef. I find this annoying. Anyone else see this?

[MattBradley]

I have seen the same behavior with constants.

[smercurio_fc · Accepted solution]

OK, so it's with a constant, and not a control? Is it that the option is not in the menu at all, or is it that it's grayed out? (If it's grayed out it means the Control Editor window is already open, and you can't open another instance of the editor.) How are you creating the constant on the block diagram? Are you right-clicking on the block diagram, selecting "Select a VI", navigating to the control and placing it? Or, do you have the Control Editor window open and you're dragging and dropping. And if you're dragging and dropping, are you dragging and dropping the control from the front panel of the Control Editor (incorrect) or are you dragging and dropping the icon in the in the top-right of the window (correct)?

What version of LabVIEW are you using?

 I can't say that I've seen this.

[PaulG.]

---

smercurio_fc wrote:

... Control Editor window open and you're dragging and dropping. And if you're dragging and dropping, are you dragging and dropping the control from the front panel of the Control Editor (incorrect) or are you dragging and dropping the icon in the in the top-right of the window (correct)?

---

Indeed. I am doing this the "incorrect" way. But why should it be "incorrect"? I save it as a typedef before I drag and drop. I will check this in the morning and get back to you.

[BillMe]

I too have dragged typedefs off their front panels directly to a block diagram to create a linked constant with no problems. Never seen them spontaneously disconnect themselves either.

[smercurio_fc]

---

PaulG. wrote:

Indeed. I am doing this the "incorrect" way. But why should it be "incorrect"? I save it as a typedef before I drag and drop. I will check this in the morning and get back to you.

---

Because the control on the front panel of the Control Editor is not the typedef. The entire container is the typedef, and you don't get that unless you drag and drop from the icon in the top-right of the window. Note that this is IF you drag and drop from the Control Editor. If you drag and drop an instance of the typedef from another VI, then it's fine, since you are "grabbing" the typedef. 

[PaulG.]

---

smercurio_fc wrote:

---

PaulG. wrote:

Indeed. I am doing this the "incorrect" way. But why should it be "incorrect"? I save it as a typedef before I drag and drop. I will check this in the morning and get back to you.

---

Because the control on the front panel of the Control Editor is not the typedef. The entire container is the typedef, and you don't get that unless you drag and drop from the icon in the top-right of the window. Note that this is IF you drag and drop from the Control Editor. If you drag and drop an instance of the typedef from another VI, then it's fine, since you are "grabbing" the typedef. 

---

I duplicated doing it my way and it did not work. Doing it your way works fine. Your explanation makes sense. Thanks.

[MattBradley]

Where I saw it was when I used the "Create Constant" with the wiring tool.

[smercurio_fc]

Were you creating a constant from a front panel control? Are you sure the control you were creating the constant from was an instance of the typedef?