Timestamp Data Type is wrong

[jon_mcbee]

The attached code is supposed to look at a cluster and read the name and datatype of each control in the cluster.  When I put a timestamp control into the cluster it returns its data type as waveform, I thought that timestamp was its own data type.  I need to get the correct data type as I am using this to populate a database.  I need to be able to differentiate between a timestamp data type and a waveform as I dont want to insert a data with waveform datatype into the database as a timestamp and I dont want to insert a timestamp into a spot where waveform data should be.  Any ideas?

 

Message Edited by jmcbee on 02-23-2009 09:15 AM

[jon_mcbee]

Forgot to attach the subVI...

[jon_mcbee]

Here is a better illustration of my problem:

 

Message Edited by jmcbee on 02-23-2009 09:36 AM

[johnsold · Accepted solution]

One of the subVIs is password protected and that is the one which generates the error.

Using the Class ID and Class Name properties seems to work OK, producing ID = 60 and Class Name = AbsTime for the timestamp and ID =47 and Name = WaveformData for a waveform control.

Lynn 

[jon_mcbee]

Thank you johnsold, I did not know that I could use Class ID and Name to get this info.  Can you tell me where I can get more info on the Class ID property, what do the values map to?

[Ben]

---

johnsold wrote:

One of the subVIs is password protected and that is the one which generates the error.

...

Lynn 

---

And that one VI is part of VI.lib so this is a bug.

A work-around could mod "get Type of Control" to handle the special case where the "ClassID" is "60".

Ben

[jon_mcbee]

I agree, I am going to implement that work around right now. 

[smercurio_fc]

I think the fundamental problem is that the type descriptors are the same (at least the part that identifies the data type). The OpenG Data Tools VI will give you the same result. I suspect it's related to a comment that Jim Kring made regarding the coloring of cluster wires.

[jon_mcbee]

Attached is the workaround I used, nothing fancy.  Just posting it incase other people come across this.

Regards

[CMal]

Here's a much simpler workaround.  No subVIs are needed.

Chris M