As far as I can see, the only property we have for selecting which cluster element is unbundled in a named unbundler is the "Element Names[]" property. But this doesn't seem to work for selecting elements out of a sub-cluster.

I've attached 2 VIs which demonstrate what I'm talking about. Open both of them and run "Test Unbundle Script.vi" - it doesn't seem to work.

Anyone have ideas?

Jaegen

Hello it does Work!?!



You can easy change the number of unbundle Elements and you can easy change their values (if they are maching to the "default" cluster)

Hmmm, maybe it only works in the German language version.

Here's what I get: (I made some minor mods to make mine look like yours)



Note: I'm using LabVIEW 7.1.1 (though it doesn't seem to work in 8.2 as well)

Jaegen

Hello It doesn't work any more

since I played around with the Methode Node (Resize, Add Output, Remove Output)

But I don't now why, it's strange.

But I am still able to select the elements in the Main Cluster (Sub 1 and Sub 2) when I then add a second unbundler to Sub 1 or to Sub 2 I am also able to select A or B. But I can't anymor directly a "Subcluster"..

Ditto here. Sometimes I was able to get to a subcluster directly, but mostly only at the same time as resizing. After a short while it doesn't seem to work except for the main cluster elements. Oh well, at least we have some part working. I might try to add all the elements with a resize next, then selectively delete the ones I don't want to try to arrive at the final desired configuration.

Shoot, there goes my theory that it actually had something to do with German vs. English, or ANSI vs. Unicode, or the like.


I thought of this, but I don't think there's a way to do this that handles everything - it has to do with the way LabVIEW handles resizes of an unbundle node in general. If you wire an unbundle by name and drag down, it automatically fills with all of the elements in the cluster, but doesn't drill down into sub clusters until you get to the end (i.e. if your last element is a sub cluster, then it starts automatically filling with the elements of that cluster - I'd love it if they changed this by the way). So, with scripting you could work out a way to get into the last sub cluster, but not any others.

Are you guys sure that you actually had this working? The end result is very dependent on which values are in the unbundle before you run, and which values you're asking for. Another annoying thing is that it doesn't return an error if you ask for something that doesn't exist.

Should I file a bug report for this??? (Or is scripting in its entirety a "bug" in NI's world ).

Jaegen

This is really bugging me. The timing is such that I was just about to start on a sub VI that needs to do exactly this.

I'm not sure if I ever got the sample VI to work, so, not calling anyone a liar, can someone confirm that it did work consistently, at least for a while? if so, I can start working backwards to try to figure out what's going wrong. any other clues would be greatly appreciated. (Fresh copy of LabVIEW, window minimized, first run only etc.) It appears a reference is getting trashed, or some data is non-persistent, but that should create an error.

The only way I have been able to do this reliably, is really clunky. I create a tree of unbundles to get the item I want and then I wire the final unbundle to the original cluster and delete the intermediate unbundles. Not for the faint of heart.

I agree, no feedback (error) for non-existent items is a real pain. As for a bug report, I remember Jeff K. saying something about "It's ok to use scripting, just don't expect us to support it", so that's a non starter.

Scripting: The final Frontier.

Very clever - I'd given up on this being possible at all (not that this is really a realistic solution though).

Joking about bug reports aside, perhaps we need someone with access to the "source code" to at least give some insight into this ...

Jaegen

Confirming!!



It worked for me yesterday perfect.

But today, it doesn't , I can't select items in sub-clusters anymore...

This post has been edited by MikaelH: Nov 24 2006, 11:47 AM

Hi scripting lovers.

Since bundle and unbundle of clusters in cluster don't work, I've had to do it in an diffrent way.

(See attached project-LV8.2).

The application is not nice written, it's just a proof of concept



Cheers,



Mikael

Interesting way to walk down the tree. I'm going to try this, and then disconnect the bottom most unbundle and rewire it to the top cluster and see if it maintains the low level unbundle. If so, then we can then delete the intermediate unbundles.

That's pretty neat Mike - consider the concept prooved