Say hi to everyone at SCI for me. We saw this same behavior in earlier versions of LabVIEW but it has been fixed in LabVIEW 7.
Tom
At 08:52 AM 2/2/2004 -0800, Dan Miller wrote:
I was wondering if someone could chime in on whether the issue of clusters linking to the first parameter with matching low level name and type. I will try to explain this using a main cluster contain 2 identical sub clusters which are defined by a constant. I am unbundling both the first element in the 2nd cluster and the entire 2nd sub cluster. I am then bundling the first element(Boolean) in both sub clusters with a constant. When I delete the 2nd sub cluster from the constant defining the main cluster, I encounter linking problems:
1. The unbundling of All Elements of sub cluster 2 is an invalid link(Name is black). I believe this to be correct behavior. 2. The unbundling of the first element(Boolean) in sub cluster 2 is now linked to the first element in sub cluster 1. In other words, LV created a new unintended connection. I believe this should result in an invalid link as well, just as unbundling All Elements
3. The bundling of the first element(Boolean) in sub cluster 2 is now linked to the first element in sub cluster 1. I believe this to be incorrect as well. Should be invalid.
This example is trying to simulate a scenario I am having using type def clusters. I have 1 large main cluster that when I make a modification to it, I am encountering undesirable linking issues. If this description is confusing, I can forward an example in LV 6.1 to anyone that wishes.
I know there were discussions on this topic last year around February, but am unaware of the current status. Is this bug reported to NI? If it has been, is it solved in future versions of LV? I am currently using LV 6.1. If someone would be gracious enough to try it with NI's latest release of LV, I would really appreciate it.
Thanks in advance for any help,
Dan Miller Sensor Concepts, Inc.
