LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

can't select items from cluster of clusters

Hello,
I have added a strictly typed cluster to a strictly typed cluster containing another s.t.cluster. When using the Select Item Tool, I have access to all elements of previous clusters using Unbundle by Name. However, I cannot access any elements of my new cluster unless I drag the unbundle tool down till my new cluster shows, create an indicator from the cluster and then unbundle by name from this indicator. Any clues? This is an area of the code I have very little experience with and I can't find clues from the manuals or the posted questions so far.
Thanks in advance for any guidance you can give.
I will attach a library made up of the *.ctl's involved.
new laser1.ctl was saved from new laser.ctl.
config.ctl w
as already in new laser.ctl.
I added ScopeConfig.ctl andthis is the one I can't get to directly.
Paul McKenzie
0 Kudos
Message 1 of 7
(3,475 Views)
Sorry, can't duplicate this one. Try deleting all instances of the outer-most typedef from the VI in question. Save the modified VI and close it.

Now just to be safe, restart LabVIEW...

Reopen the modified subvi and reinstall the strict typedef in it and see if the unbundle by name works.

Sometimes, changes to complex typedefs don't always propegate as they should. See if this relinks things correctly.

Mike...

Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 2 of 7
(3,475 Views)
Hello Paul,

I have splitted your cluster into it's parts without having problems; but I use LabVIEW 6.1
Find attached a jpeg-file with screenshot of diagram, this shows how I did it.
Maybe you can see a difference to your solution......

regards
wha
0 Kudos
Message 3 of 7
(3,475 Views)
I'd like to thank Mike & Wha for their responses.
Mike, I tried removing, closing , and reinstalling the typedef, but no-go.
Wha, your diagram did help. I had been hoping to unbundle directly, but using the inserted unbundle(no names) works well enough for now... it's still puzzling why some elements will show and others won"t...
Thanks again,
Paul
0 Kudos
Message 4 of 7
(3,475 Views)
I can' t explain this feature, it looks like a bug.
I succeeded to access the disabled items in the list by selecting an item near ScopeSettings and enlarging the node until it shows the desired item.

Usually, items are disabled when there is a name conflict, as in the small cluster example.


LabVIEW, C'est LabVIEW

0 Kudos
Message 5 of 7
(3,475 Views)
Jean-Pierre,
It was interesting that your example had the abreviated labels as if the cluster had been accessed directly. When I popped up the unbundle tool and navigated down through the expanded menus, I could not access directly. Using yor idea of starting with an entry close to the desired cluster and expanding, the names were always complete for me, ie they included all the levels of clusters seperated by dots. How did you get the abreviated names only? I know this can be done by using the unbundle (no names) first, but I can't get it to happen directly. I'm using 6.0.2, would behaviour be different in 6.1?
Thanks for trying,
Paul
0 Kudos
Message 6 of 7
(3,475 Views)
Right click on the Unbundle node and select "Hide Full Names" to hide the names of the parent clusters.


LabVIEW, C'est LabVIEW

0 Kudos
Message 7 of 7
(3,475 Views)