LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Variant from a queued cluster

One more suggestion...if you are comparing type descriptors purely as a datatype comparison, you can use the VIs in vi.lib\utility\GetType.llb to get an enum describing the datatype of the control/variant/I16 array that you wire in.  GetType.llb is only available in LabVIEW 7.0 and later, although I'm guessing if the VIs were Save For Previoused they would work in earlier versions.

-D

Message 11 of 16
(956 Views)
Yes the data name is included in the TD. If you want to play with variants, I strongly encourage you to use the OpenG Toolkit downloadable from OpenG.org. It includes a set of tools to manipulate variants, such as extracting the dataname.

Message Edité par Jean-Pierre Drolet le 02-14-2006 01:04 PM



LabVIEW, C'est LabVIEW

Message 12 of 16
(945 Views)
OK, sorry, I misunderstood what he was asking. I thought he was talking about what gets displayed on the variant control itself. Yeah, all that info is in the typedef and I agree that if he really wants to go this route he should definetely use the OpenG toolkit for variants. It requires a bit of code to get to that information...
0 Kudos
Message 13 of 16
(938 Views)
Just a quick update,

I've implemented a small program to "clean" up the TD so that comparisons between block diagram onstants and Typedef controls are valid.  I've learned a bit about TDs in the process, but I've steered away from the OpenG versions, as I want the code to be unencumbered.  OpenG packages are still released under GPL are they not, thus prohibiting commercial use without exposing the source code.  I'd rather avoid this, especially since basically everything you need is in the help files.

Having said that, there are some funny goings on when dealing with TDs........

Shane.
Using LV 6.1 and 8.2.1 on W2k (SP4) and WXP (SP2)
0 Kudos
Message 14 of 16
(906 Views)
OpenG is released under LGPL that means that you can distribute your closed source code using OpenG libraries. The only obligation is to distribute linked OpenG VIs in open source so the end user can eventually modify or update them. This is easily done using the OpenG Builder that builds your application with OpenG VIs stored in in a separate LLB with FP and BD. The rest of your application can be built as you wish, allowing multilple destinations (EXEs or LLBs) with/without FP/BD.

So feel free to use OpenG for your distributed applications. You'll enjoy these OpenG popup banners while running your application (kidding Smiley Very Happy)

Message Edité par Jean-Pierre Drolet le 02-23-2006 06:23 AM



LabVIEW, C'est LabVIEW

Message 15 of 16
(900 Views)
Jean-Pierre,

Thanks for that clarification.  I wasn't aware of that quite significant aspect of the LGPL.  I'm not a lawyer and have trouble interpreting such things.

I WAS kind of wondering how come the tools were so popular otherwise......

Either way, I've learned a lot about Type descriptors which I wouldn't have otherwise known.  It didn't take long to implement after all.

By the way, since I've been lacking presence in the "Congrats" threads, congratulations on reaching another milestone.  It hink it's safe to say you have an extensive knowledge of all things G and this coupled to your willingness to share is literally awesome.

Shane.


Using LV 6.1 and 8.2.1 on W2k (SP4) and WXP (SP2)
0 Kudos
Message 16 of 16
(891 Views)