Always break Unbundle or Bundle by Name when the item in the cluster is removed.

[Brandyn]

One of my pet peeves when using the Unbundle or Bundle by Name occurs when I remove or add an item from a cluster and LabVIEW attempts to find the item with a similiar name.  The behavior should always break when the specific item in the Unbundle/Bundle by name is removed.

More often than not LabVIEW picks the wrong thing and introduces programming bugs. 

[EricC.]

A intersting idea, but in some case, when you understand how work LV, you win time when you can deactivated this function and if you let do LV in automatic.

EricC

[JKSH]

@EricC

I think he meant break the connection when an element is removed, not renamed.

If I rename an element, I want LabVIEW to rename all by "(Un)Bundle-By-Names" too. But, if I remove an element, there's probably no chance that LabVIEW can pick a suitable replacement.

[Brandyn]

@JKSH and thats the problem, LabVIEW sometimes attempts to find a suitable replacement and it sucks at doing it.

[Kiesch]

It should be configurable (with default off). For just renaming - it's practical. But in some cases Renaming means repurposing - and if you miss some unbundle wants to do something with the old meaning - you're f***ed. Turning the feature off would just lead to: make change --> follow and correct all errors.

Especially for LVOOP this is really important (in my opinion), since you either have to work with unbundle / bundle or setters an getters (in my case I typically contain the problem inside the setters and getters - making debugging on changes easier; but for time critical applications it might be more practical to use inline unbundling).

[_Y_]

Great idea. Almost all attempts of LabVIEW to "guess" the code result in errors that are difficult to find. I would say that renaming must not result in errors but removing musyt always do. Even more: removing an element then placing another element with the same name must not "repair" the brocken wires.

Of course it will require more time at coding but saving more at debugging.

[Brandyn]

Yea.  This idea was born out of times debugging when LabVIEW tried to "help" me

[Intaris]

Oh I fully support this idea.  I HATE it when LV automatically re-assigns things for me.  It's got a 110% chance of getting it wrong. (or so it feels).

These changes (although well meant) can lead to some really annoying prolonged debugging sessions.