LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
0 Kudos
ouadji

Property Node : type specifier refnum

Status: Declined

Any idea that has not received any kudos within a year after posting will be automatically declined. 

                 I am maybe going to say something stupid (??)  Smiley Frustrated


          but ... to get dynamically the Ref of the type specifier


    would it be really impossible to have a Property Node like that?

 

SR1.png

5 Comments
CMal
Active Participant

The purpose of the type specifier terminal is to statically define the connector pane and type of the VI being used so that any downstream "Start Asynchronous Call" or "Call By Reference" nodes will have their connector panes updated.  The runtime value of the type specifier wire isn't even used.  Only the data type is used, and by definition, data types are defined at edit time.  I don't think what you're suggesting is possible.  What problem are you trying to solve with this idea?

ouadji
Trusted Enthusiast

hello CMal,

 

What problem are you trying to solve with this idea?

 

be abble to put an asynchronous call within a sub-vi,

and then be able to use this sub-vi from different vi references.

(Different sub-vi that don't have the same connector pane.)

Intaris
Proven Zealot

Your "VI Ref" input to your sub-VI would already have to be a strict reference of that type thus completely destroying your intended purpose of reusability.

 

You cannot have a Typedef unknown at runtime because that's not how LabVIEW rolls.  It requires strict data typing which is the opposite of what you're trying to do.

ouadji
Trusted Enthusiast

thank you for this explanation
So, it's impossible. Understood.

Darren
Proven Zealot
Status changed to: Declined

Any idea that has not received any kudos within a year after posting will be automatically declined.