Ability to Split "Unbundle by Name" into Two Parts

[dthor]

It would be quite convienient to be able to split "Unbundle by Name" into two separate nodes. To do so, the user would right-click on the seperation bar between items in the node, and select "Split Here". The cluster input would be attached to the new node, and all the output wires would remain the same.

This would allow for easier code refactoring and cleanup.

The inverse of this could also be implimented (though a seperate Idea): Moving two "Unbundle by Name" nodes together optionally joins them, provided they both have the same cluster as an input.

[PaulG.]

I do this manually nearly every day. Good idea.

[labview4steve]

Simply genius!!!

[asbo]

I don't think this is a very useful feature addition. Splitting unbundles is extraordinarily easy (control + drag, resize, resize). Combining might be useful, but it's not a very functional feature, and only marginally improves IDE workflow. Honestly, I can't ever think of a time when I needed to merge unbundles.

[dthor]

> Splitting unbundles is extraordinarily easy (control + drag, resize, resize).

You forget about rewiring though. Rewireing can be quite a time sink if there are more than, say, 5 nodes in the unbundle. This Idea is supposed to remove that annoyance.

And plus, in my opinion a bunch of minor IDE improvements can sometimes be worth more than one big improvement.

[David_Staab]

Using two unbundle nodes instead of one might cause a performance hit. Can anybody from NI verify that it would not?

[dthor]

> Using two unbundle nodes instead of one might cause a performance hit.

It seems like this is something the compiler would be able to take care of. Even so, if it *does* cause a perormance hit, I would still use the feature. None of my code needs to run super fast 

[SteenSchmidt]

@David_Staab: Two unbundles instead of one shouldn't impact runtime performance in any way. Clusters in LabVIEW are almost exclusively a programmer's aid at edit-time, with the sole exception that they force their elements to occupy contiguous memory which the same elements, if left outside a cluster, would not have to.

So an unbundle is basically just replaced with pointers to some memory addresses by the compiler.

Cheers,

Steen