Weirdest bug...

[wiebe@CARYA]

So I though I'd make a refresh option...

The 2nd loop iteration, there are no results though.

I added a MessageBox for a debugging:

First time, I get FALSEFALSEFALSE, 0. As expected.

I was expecting (although that would still be a puzzle why)  TRUETRUETRUE, 1 the 2nd run.

However, I get TRUE, 1!

How is it possible that the array changes size over iterations??

(Obviously I'm not manipulating wire sources, LVDS, pointers etc. It's all plain LV, except it runs in the short cut context)

EDIT: It gets weirder:

1st popup: FALSEFALSEFALSE, 2

2st popup: FALSE, OK

Something's seriously wrong...

[Darren]

I agree that looks very strange. Send me a PM or an email with your plugin that is exhibiting this behavior if possible, I'll take a look.

[wiebe@CARYA]

I found out that when I "Call And Forget" the VI (in a plugin's execute), the bug is there. I keep hearing good things about it, but every time I try it there is trouble...

It doesn't happen in normal context space.

If I call the VI as a SubVI, or dynamically with the Run method, the bug isn't there.

The code is developed in LV24 and stored as LV19, not sure if that's a factor too.

I think I can even make a SSCCE (not now though). EDIT: I did move on, so it might not surface again.

Found a Busy Cursor bug too, but that's literally another problem.

[Darren]

Definitely sounds related to the reference lifetime change that went in recently... if you try dynamically launching VIs from a right-click plugin, any references that are passed around may be closed by LabVIEW. The workaround is to pass non-reference data into the dynamically launched VI that gives you enough info to re-create the references you need.

[wiebe@CARYA]

I would have understood the closing of references. They are copies, so the debugging was actually added to investigate why this didn't do the trick.

Even if the references become invalid, this should not ever empty the array!

The empty array should not cause the MessageBox to show OK, while the array size is 0!

It seems to me the terminal's array pointer is set to NULL, causing the weird problems.

I'd think the TLDS is somehow corrupted by the combination Call And Forget and the exotic context.