Shared reentrant VI uses static registration of application event

[Cranky]

I'm upgrading a project from LV2011 to LV2014 and have hit a snag. I've got a reentrant VI that is throwing an error for statically registered application events. Is this a bug when upgrading from 2011 to 2014? The execution options are different between the two versions. Is this possibly a bug when upgrading?

[Bob_Schor]

Don't know.  Attach the VI so we can inspect and "play" with it -- maybe we can "fix" it, but without "seeing the problem", it is difficult to "see the solution" (except to say "Something is Not Working", but you already know that ...).

Bob Schor

[Cranky]

Looking at the events, there's another strange message. The warning at the bottom indicates there's something amiss inside of the VI.

[Bob_Schor]

OK, better attach everything.  Take the folder containing all your VIs, and Compress it (which creates a .ZIP copy).  Attach the .ZIP.

Bob Schor

[Cranky]

As mentioned in the other thread, the project is almost 750 MB. I'll see if I can peel out just the offending VI and post that.

---

@Bob_Schor wrote:

OK, better attach everything.  Take the folder containing all your VIs, and Compress it (which creates a .ZIP copy).  Attach the .ZIP.

Bob Schor

---

[Cranky]

Here's the stuff for the class. There's probably going to be lots of broken wires.

[Cranky · Accepted solution]

Aah, the joys of developing shared code! Turns out that the VI heirarchy is dynamic dispatch, not static, and trying to call the Application Instance Close? event (which is apparently static) causes the error. Deleting the event case clears the error.