Event structure updates poorly when changing events connected to the "Reg Events" node

[crossrulz]

---

@raphschru wrote:

I also tested with LV2016 and LV2018 and it behaves exactly as I showed for LV2020.

So the "bug" was always there.

---

I'll see your LabVIEW 2016 and raise you to LabVIEW 8.2.1.  Yep, same behavior.  So this is likely something that has been there since the dynamic registration came out.

But something I did notice with the control registration one: The event index changes to "<?>".  In the other versions I tried, it would say "<3>".

And just noticed while playing with it in 2016 that if the User Events have different types (ie I changed the "Other Event" to a string), it works perfectly fine.  So this appears to be related to finding the first event with the correct data type.

[billko]

If you delete the wire going to the dynamic event terminal before adding the new event to the top, then reconnecting it, it seems to work.  However, this does not work for the one with the array of control refs.  I wonder if that is somehow related to the fact that it's an array?  At any rate, it ain't workin' right.

[DerrickB]

I've alleviated this issue somewhat by grouping event refs into clusters to use with the registration and I can't recall as many headaches around this ordering. Otherwise I've skipped caring about wire overlaps to always add new items to the bottom.

[raphschru]

Grouping refs into clusters only makes it more complex to maintain, and the reordering problem is still there.

Here with user events:

With controls it's even more vicious, you have to touch the Reg Events node to bring the bug to light:

[DerrickB]

Not the control refs, the event refs. I'll nab a screenshot when I get a chance.