bug Get Default Data from Variant

[Jim Kring]

There's a VI in the lvdata package called Get Default Data from TD (that accepts a type descriptor input), but there's no equivalent (wrapper) for variant data input. I suggest that a Get Default Data from Variant VI be added to the library, for symmetry (and the fact that it would be useful -- I've needed such a function recently).

Get Default Data from Variant.vi

[jgcode]

This is a very simple (wrapper) VI that would be a nice addition to the OpenG LabVIEW Data Library.

You can track this item here: ID 3411324

Here are the submission details:

Get Default Data from Variant.vi

TEST - Get Default Data from Variant.vi

Code is in LabVIEW 2009

[Jim Kring]

Hey Jon,

I'm not sure if putting it in the Type Descriptor subpalette is the best place (since this palette is for VIs that take Type Descriptors as inputs). I think that it probably makes sense to put it on the main, top-level palette.

[jgcode]

Hey Jon,

I'm not sure if putting it in the Type Descriptor subpalette is the best place (since this palette is for VIs that take Type Descriptors as inputs). I think that it probably makes sense to put it on the main, top-level palette.

Roger.

Unfortunately that spot is already taken

I will have to drop it down a row.

There is also a VVariant palette (which is what the output is)?

[Jim Kring]

Roger.

Unfortunately that spot is already taken

I will have to drop it down a row.

There is also a VVariant palette (which is what the output is)?

Hi Jon,

As long as it's somewhere on the root palette, I'll be a happy camper

But, I don't think it should go on the VVariant palette, since that is for VIs that deal with variant data (at run time) inside of the variant inputs/outputs (at edit time). It makes sense if you think about it really hard, but is guaranteed to make your head hurt.

For example, in the snippet, below, you end up with a VVariant (a Variant containing a Variant containing a String).

[jgcode]

Hi Jon,

As long as it's somewhere on the root palette, I'll be a happy camper

But, I don't think it should go on the VVariant palette, since that is for VIs that deal with variant data (at run time) inside of the variant inputs/outputs (at edit time). It makes sense if you think about it really hard, but is guaranteed to make your head hurt.

For example, in the snippet, below, you end up with a VVariant (a Variant containing a Variant containing a String).

Yes, sorry you are correct - it is a VData not VVariant output.

I will add it to the root palette, no dramas.

Cheers!