Removing terminals from unbundle

[AeroSoul]

Hello

This is a question stemming from finding this on Idea Exchange (but didn't want to derail the thread there).

Is there an easy way to remove an un-needed terminal from bundle/unbundle cluster function?

Sometime it happens that i don't need a terminal anymore... and it always happens that it's in the middle of bundle/unbundle function, so i have to rewire the entire thing.

[Henrik_Volkers · Accepted solution]

For me a rigth click on the unwanted terminal and remove element or remove input works fine 😄

[AeroSoul]

Alright...

Wonder how much time i would have saved if i just right clicked the damn thing 😄

[Bob_Schor]

---

@AeroSoul wrote:

Wonder how much time i would have saved if i just right clicked the damn thing 😄

---

Don't feel bad -- I use Unbundle by Name just so I can "get the terminals I want", being also blissfully unaware that you could "selectively" unbundle (and bundle, too?).  Still, Old Habits Die Hard ...

Bob Schor

[pincpanter]

---

@Bob_Schor  ha scritto:

---

@AeroSoul wrote:

Wonder how much time i would have saved if i just right clicked the damn thing 😄

---

Don't feel bad -- I use Unbundle by Name just so I can "get the terminals I want", being also blissfully unaware that you could "selectively" unbundle (and bundle, too?).  Still, Old Habits Die Hard ...

Bob Schor

---

Yes, you can also selectively Bundle. A big plus of Bundle/Unbundle by Name (IMHO) is that you can find them with a text search.

[LVNinja]

You need to make your orginal control (the source of your bundle/umbundle operation ) as Type Def, 

to do that, right click on the control and select MAKE TYPE DEF 

Then OPEN TYPE Def. This will make that acontrol into a CTL file, where all the information about that control is stored. 

Then from each vi you are using that control, use that CLT control (just copy and paste from the VI where you create the type def. 

Then if you change that CTL file, Type Dev, everywhere else where you use that CTL will follow the format. 

For example if you remove one component of that CTL cluster, everywhere else where you use with unbundle will automatically follow without the need to update that. 

Open the 2 vis I attached, then open the Control1_clusterType Def.ctl, and delete any element, it will automatically upade the vis using that clt. 

[altenbach]

On a side note, the plain bundle/unbundle (i.e. NOT "by name") cannot be resized, but you don't need to wired all of the element inputs if the input cluster is wired. In that case, unwired inputs are simply ignored.

For example, the following code is not broken and works fine.

Still, I almost always use "by name" because it creates more readable code.