LabVIEW Style Challenge - Error Wires

[hunter_jki]

I'll play too

[_Henry]

[Hooovahh]

I assumed the Queue and Event were independent processes and should be generated even if one fails.  I also assumed that this doesn't need to scale up with more parameters, but that seems like a place for improvement with a for loop.

[crossrulz]

And here is mine. 

[JÞB]

Hooovahh,   did you right-click the merge errors and report all?  I think there is another glyph that would be visible if you did.  I could be wrong. 

But, I definitely advise adopting this new feature and would be disappointed if it was overlooked at GDevCon. 

[altenbach]

Here's what I might do:

Of course we don't really have all requirements, for example should an error be generated if an item is not found or should it just ignore missing values??

[Kyle97330]

I may make a submission later, but I see that a couple of the existing submissions have used an Error Ring.

The error ring is great in theory but in practice it is an Xnode, which are now recommended that you not use per Darren in his presentation "Ludicrous ways to fix broken LabVIEW code", here:

https://youtu.be/HKcEYkksW_o?t=602

The short version if you don't watch the whole thing is that Xnodes may work well in isolation but can and will cause incredible headaches when they start being used in classes, PPLs, and malleable VIs, but the cause will often be nearly impossible to trace back to your use of an Xnode.

[Hooovahh]

---

@JÞB wrote:

Hooovahh,   did you right-click the merge errors and report all?  I think there is another glyph that would be visible if you did.  I could be wrong. 

But, I definitely advise adopting this new feature and would be disappointed if it was overlooked at GDevCon. 

---

It does not have merge errors.  I thought about it but I thought in cases you might get the same error reported twice due to the wiring.  But it probably is important for the User Event, and Queue to have unique errors tracked.  In practice it doesn't really matter because even one missing reference is bad and needs to be fixed, knowing you have two might not help debug it much.  But yeah what harm is it to just have it on?  Not much.

[mcduff]

Interesting, quite a bunch of impressive people on the submission list. My questions/observations:

1. Surprised nobody specified a default value for the INI read.
2. If the key is not found or an error, most do not send a message on the User Event or the Queue. What happens if the receiver is waiting for a message? Why not send a default value or a key not found message? Why not notify things downstream of the problem?

[Gregory]

Pet peeves: stuff hidden under structures, wires going from right to left, default subVI icons.