Jump to content

Variant To Data automagically backwards propagating type


Recommended Posts

Hi all,

 

I remember some time ago a discussion somewhere (cannot remember where) about the possibility of a Variant To Data figuring out which data type to output depending on what type the output was wired into.

 

Even though the type input is shown as a bold input (i.e. "required"), it is possible to leave this off. I have always manually placed down the desired output type, just as a force of habit more than anything else.

 

It seems that as long as there are no other structures in the way the Variant To Data is able to figure out the type it is being wired into, so is there any sense in placing a type constant?

 

Interested to hear what others do here.

Edited by Neil Pate
Link to comment

Your Google-fu fails you. 

 

https://lavag.org/topic/16197-magical-variant-to-data-or-bug/

 

It seems it is not in all circumstances.  Personally I like this kind of feature, assuming you can always override it with the Data Type input.  I took this concept and used it on my Variant Repository XNode, which has a similar feature where it looks up stream to try to figure out what data type it should be.  Sorta like a polymorphic VI having the Automatic option.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.