Bundle Swap.llb (works on unbundle also)

[wiebe@CARYA]

Author: Wiebe@CARYA

Here's a RCF plug in that swaps a (Named)Bundler to (Named)Unbundler and vice versa.

As suggested in this idea: Add "Change all to Read\Write" to bundle\unbundle 

It's a first attempt. The (re) wiring is a pain, and could probably be improved.

Before:

After:

Attachment is saved in LabVIEW 2018 (and zipped for LV15. For install instructions, go here

[parthabe]

Hi Wiebe,

Is this an "Edit-Time" or "Run-Time" plug-in? please clarify.

[parthabe]

Hi Wiebe,

This feature is working as expected. Thank you! 🤝

However, after selecting the shortcut menu, both the elements were replaced by the same element, in this case, TC_Names.

[AristosQueue (NI)]

Weibe: please update this post to use this template to describe your tool: https://forums.ni.com/docs/DOC-43461 It helps people sift through plug-ins that they want.

[parthabe]

Wiebe,

I encountered another problem today. Right-clicking on the Unbundle/Bundle node pops up this (unwanted) dialog first, and then shows up the Context Menu items upon clicking Cancel/Revert.

Could you look into this issue?

[wiebe@CARYA]

>Weibe: please update this post to use this template to describe your tool: https://forums.ni.com/docs/DOC-43461 It helps people sift through plug-ins that they want.

I'm not sure why I didn't get the template. I got this automatically with previous posts... I'll try to rectify.

[wiebe@CARYA]

@Partha (naming issue)

I've get the same problem with the names changing. Not sure if I got that before, I think I would have noticed. The normal (manual) replace does this too. I guess I have to get the elements and restore after the replace.

@Partha (popup dialog)

I thing this is because I didn't  separate source code. I'll change this if I update the first issue. I hope this will still be set when saving back to 2015, the save to previous seems to revert this option in some situations.

[wiebe@CARYA]

@Parta

The code separation was already on. Not sure where that popup comes from. I don't think it's a VI that I use.

[AristosQueue (NI)]

That dialog says that you have edited that plugin on disk during this run of LabVIEW after the plugin was used once. It's a problem on the user end, not the NI end. You can run the Refresh VI ( resource\plugins\PopupMenus\support\Refresh Menus.vi ) to fix it or just restart LabVIEW. If it keeps happening, it likely means someone tried to write a plug-in that rescripts the plugin itself.

[wiebe@CARYA]

That VI is now shipped with LabVIEW (All Controls and Indicators and All Constants menu items). 

Is it certain the VI is the cause?

Does this mean someone is scripting a LabVIEW VI?

Was this there in LV16 (if not, it's probably downloaded as LV15 VI)?

[parthabe]

Wiebe >> "The normal (manual) replace does this too."

Not only that, it also makes the node jump down by quite some pixels, almost the height of the one element of the node. If someone has to move down such a node all the way down the screen from the top, but is in no hurry to do it immediately, s/he can do this way! 😄

Wiebe >> "I thing this is because I didn't  separate source code."

No, you have separated it! I just saw that, that option has been selected in the VI Properties.

Wiebe >> "the save to previous seems to revert this option in some situations."

I think one of them is, when we down-convert from 2016 to 2015.

[wiebe@CARYA]

Hmm.

Don't use this on an event data node (bundler\unbundler). It will swap, but with empty elements (as there is no wire attached).

You can now delete it. A line remains. You'll never get it back...

Even in LV2020 if you hide and show it, it won't help.

Wire something to the bundle, LV crashes.

Guess it needs a bit more TLC to prevent this menu on an event data node...