Automatic Type Specificer

[Valarauca]

When working with a call by reference, one needs to use a strict reference (so to include front panel objects).

But the problem I'm having is making a strict reference. I need to select VI server class, browse to the VI's location, and then open the VI.

Wouldn't it be possible just to use the file I'm already using to open the VI's reference.

aka

Is there a way to automate making a stritic reference to a VI for the call by reference function?

[tst]

Yes. Drop a Static VI Reference (from the app control palette). Drag your VI into it. Right click it and select the strict option. This has two other advantages in that it loads the VI into memory (and will automatically include it in a built application) and it allows you to use the VI Path or VI Name properties from the static ref to input into the Open VI Reference function.

[Darin.K]

You can drag a VI icon onto a Static VI reference to create a reference, you will have to right-click and choose to make it strict.

[Valarauca]

Oh never mind I'm an idiot. 

If I want to execute a VI based purely on its path I'll have to use an Invoke Node to Call by Reference. Other wise if I make a Call my Reference node I'll have no way to automatically set it's inputs to my specified inputs. 

Or will I?

[Valarauca]

You seem to be missing the point. 

I don't want to click, I want to make the status automatically based on a path variable. \

Aka make the reference without any click or dragging, have the call be set up automatically without right clicking, or dragging. 

[tst · Accepted solution]

If you want to use the connector pane, you MUST have the strict reference and every VI which you use there will have to have the same connector pane, or you will get an error. I'm not sure why dragging a VI once is difficult. If you want to have multiple VIs, just use one of them as the input to the type specifier (or you can even disconnect it, but I don't feel like describing that process) and obtain the path separately.

If your VIs have different connector panes, then you can't use CBR to call them and you will need to use the Run VI method as you suggested.

[Valarauca]

It's not that it's difficult it's just I wanted it to be done automatically by a different function because I didn't see why I couldn't (or why it shouldn't be possible)