Search the Community
Showing results for tags 'references'.
Found 2 results
Hello, I have two reference clusters that are strict type def. and I need to merge them into one but keeping the Labels of the objects. This is just an example because I have a larger code with several objects and I need to merge references clusters into one, since many SubVIs have unbundle by name functions already setted. It is a long story. LOL I don't need to have it happening on run time, it can be done before allowing me to create one single reference cluster that I will feed to my unbundle functions into the SubVIs. Find below a picture showing what I want to achieve. Thanks. Dan07
I ran into an interesting issue with the Array of VData to VCluster when using XControl references as part of the VData. It looks like it puts it together correctly into a cluster, but when trying to type back to the XControl reference type it throws an error. You can convert it back to a normal control type, but when doing generic sets on controls in a cluster that method doesn't work very well. LV2011, Latest verison of the library. Screen shots here and code attached. I actually tried it with a couple different XControls and it didn't work. I wouldn't think that this behaviour is normal, but maybe there are some known restrictions when using XControl references? The references themselves seem a little weird because I did a source build on the project and it changed the type of controls in the "new" cluster constant when LabVIEW compiled it. They were just normal control references made from scratch in the source code and then in the build it changed them. They still said "Control" but when you clicked on them to view the ActiveX class they had Control and MRUFilePath selected. Weird. Anyway, I can probably manually cast these values, but the whole reason behind my method was I just had to add the control ref to a cluster in a class and input the refereces as a variant array and It would load them...no custom loading of the clusters. XControlRef.zip