Merge Errors.llb

[JW-JnJ]

Author: JW-JnJ

Makes error wire handling a bit easier.

1) Select sources and one destination. It will create the merge error and wire up the rest of the selected sources.

Note: It will select the right-most non-source and non-wired terminal.

2) Select an existing wire and new sources. It will insert a merge error at your right-click location then wire the rest of the selected sources.

3) Select a merge error and new sources. It will expand the merge error and wire all new sources in.

These were listed in reverse priority. It will check for an error node selection first, then an error wire selection, then just default to finding the destination and creating it's own.

If you hold CTRL before right clicking and while clicking Merge Errors, the existing merge error and existing wire will insert the error in the bottom and top of the merge error node depending on if it is above or below on the diagram.

Attachment is saved in LabVIEW 2016. However, I am not sure when the "Is Error Cluster.vi" was introduced, so it may not work for some versions.

For install instructions, go here.

Edit 8/2/21: Fixed the problem of the rightmost node having a source. Added CTRL functionality for sorting error priority. Also changed the plugin affected objects from GObjects to a collection of slightly more specific GObjects

[crossrulz]

---

@JW-JnJ wrote:

Attachment is saved in LabVIEW 2020 for now.

---

You have to use a project with the llb in it.  You then save the project for previous and the llb will be converted.

---

@JW-JnJ wrote:

and it uses the newer type identification functions so I'm not sure how far it can be back-saved)

---

The Is Error Cluster.vi was introduced somewhere between 2016 and 2019.  I don't currently have 2017 or 2018, so I can't check those.  And I can't find anything mentioned when I searched the upgrade notes.

I have this currently working in 2019.  I think this will be useful.

[JW-JnJ]

Thanks Tim! That worked. I uploaded a 2016 version and will update the document once we find out where the version line is.

Edit: huh, kudos to a comment shows up on the document kudos. Virtual kudos Tim! Feels weird for me to make my plugin look like it has a kudos

---

[Petru_Tarabuta]

Thanks! I used the tool briefly this morning and it is very useful. Will continue to use it. I have added a link to it in List of Community Shortcut Menu Plug-ins (Part 2) .

[JW-JnJ]

So I was thinking about error priority for this plugin. I had a few questions for the people using this 

• For the existing wire case, I would assume a default of having the existing wire being higher priority is good?
• For an existing merge error node, would people like the ability to hold a key and have it insert at the top? (Not sure if that's possible)
• For the existing merge error case, maybe sources above the merge are inserted above instead of the above option. This just relies on you sorting priority vertically first.