Leaderboard

I was mucking around in General Error Handler.vi today and noticed a weird subVI with a really intersting comment inside. Thought I'd share it with the crowd, since it applies to time-critical processes, thead swapping, and general compiler insights.

Yes, this is exactly what I am experiencing. Creating the child class from within a LabVIEW project window works fine in LabVIEW 2013. Creatind the child class from within a Class Project Window crashes LabVIEW 2013.

Sorry, an extra comment. I have just found the following paragraph.... "One parameter that you probably want to pass the clone is the new clone’s own VI reference — the one created using the Open VI Reference function. This is a very special reference, because (unlike an implicit VI Reference ) closing it will cause the clone to stop executing immediately — killing the VI dead in its tracks. Generally, you will want to pass this to the clone, so that the clone can be in charge of closing it, when it completes execution." Found here: http://thinkinging.com/2007/03/29/reentrant-vi-clone-name/ OK this is an old document and discusses LV8.2.1 mainly, but does anyone do this? Do you really pass a clone VI its own reference as a parameter and then set the VI to close its own reference?