Yes, the OpenG solution using the "ClassID" property is nice however you can also use the "ClassName" property. This will give you a plain english word describing the class. You can then feed this into a case structure as a string. It will only take a few minutes to figure out the class labels.
If you are curious and want to dig deeper into Type Descriptors. NI has a nice App note on this here: <http://zone.ni.com/devzone/conceptd.nsf/webmain/370DFC6FD19B318C86256A33006BFB78?opendocument#3> Michael Aivaliotis <http://forums.lavausergroup.org> P.S Has anyone else been getting messages as attachments in their inbox from Info-LabVIEW or is it just me? If so, what's going on? > Another option is to use the ClassID property to figure out > the type. In the OpenG toolkit there's even a nicely defined enum. > > Jason > > >Hello > > > >I am doing a little research on references to front Panel > >Items. If you get > >an array of references to the controls (and Indicators) on the > >front panel > >you can get their label text out rather easily. The value > >however is held as > >a variant and can be extracted if you know the type. > > > >Preliminary testing indicates that the "Type Desc" property is > >an array of > >16 bit integers. The second column seems related to the type > >of the control. > > > >16417 is boolean > > > >16394 is numeric double > > > >16387 is numeric i32 > > > >16434 is Path > > > >15432 is a string. > > > >I do not like compiler archaeology. Does anyone have a better, > >perhaps even > >official, list, maybe even a program to scan the type desc > > > >Yours Sincerely > > > >John
