Problem with VIs saved without the diagram when loaded from the controls palette

[Helene]

I've developed an extended control (with diagram code), I saved it without the diagram, and loaded it in my control palette.
In a new VI, when I take this extended control from my control palette and run my VI, the control won't work at all : nothing happens, just as if the diagram code was not stored with my specific control.

The reason why I want to do that, is to be able to create an HMI with extended controls, and have the possibility to add and delete extended controls without touching to the diagram. At the moment, when I delete an extended control from my HMI, I need to remove the corresponding code on the diagram.

Any idea?

[Greg_McKaskle2]

> I've developed an extended control (with diagram code), I saved it
> without the diagram, and loaded it in my control palette.
> In a new VI, when I take this extended control from my control palette
> and run my VI, the control won't work at all : nothing happens, just
> as if the diagram code was not stored with my specific control.
>

From what you describe, it sounds like you wrote a VI for your HMI
control, and you are using the Merge option to drop both panel and
diagram elements when the HMI control is dropped from the palette.

When you do not save the diagram, LV literally doesn't save the diagram,
and so the merge is only of the front panel. In neither case is the
compiled code of the HMI VI ever involved as LV doesn't currently have a
way o
f having a control "run" its code. You can often put most of the
HMI code into a subVI, which will help, but you cannot get rid of it
completely.

At the moment, what you describe is not possible, but it is a goal of
ours.

Greg McKaskle