lvb

In the TestStand Variables view, insert an "Object Reference" variable.  One thing to keep in mind, this terminology is confusing because it only stores a "copy" of the data in the variable (since LVOOP is by value).  You must pass this variable in and out of all methods of the class.

An example on the NI website:

TestStand Using LabVIEW OOP Truck Example

IN either case the shift register should be removed. In error in closing one reference should not prevent others from closing.

I don't believe it will.  There are several functions (like Close VI Ref) that will function even if an error is passed in because it knows it is a cleanup operation and should try to run no matter what.

As hooovahh said, it doesn't change the behavior in this instance.  It also makes the diagram cleaner.

FYI, I always pass the error wire as a shift register with a loop.  If the loop doesn't run (i.e. empty array auto-indexing), tunnels will "clear" any error on the wire.  This is a very common bug I see in applications.

The only time I ever need to do this kind of thing is when the app is exiting. Then I just don't bother and let LabVIEW clean up my mess.

Doesn't this make debugging true memory leaks a needle in the haystack situation?

Create a Base class for the Events and inherit it for all the different type.

It’s lot of work but that makes it possible to destroy them using a for loop.

Thanks also, I should probably change my original post to state I am looking for the solution that requires the least amount of "coding" time but yet still performs everything in parallel.

I think the best answer is to create a scripting VI.  It would be nice if LabVIEW had a "close cluster of events" primitive.

So my official solution is to change your architecture to either have all user events user the variant data type.  Or only have one user event with the variant data type.  And in both situations convert back to the usable data type where the data is used.  Sorry I couldn't come up with something better.

Thanks for taking a look.  Your work-around seems to be more work than just adding the extra code to close the events.

There has to be a better way of doing the following, so I thought I would query the hive mind of LAVA.  Please note the user events have different data so the cluster to/from array functions will not work.

Separated compiled code has been working well for our team over the last 3 years.  There are two instances where we encountered issues:

• Packed Project Library build corrupting the VI Object Cache
  • The VI Object cache had to be cleared after PPL builds
    

  [*]TestStand with the LabVIEW Run-Time adapter requires uni-file code if distributed as source
  

-Brian

I highly suggest reading daklu's (Dave Snyder) various posts on Lava and the NI community.  This is a good start:

[NIWeek 2013] What a Software Architect Needs to Know When Using the Actor Framework

-Brian

My understanding is as follows:

If your certification was "active" (not suspended) on March 3rd/4th, it will be extended.  As crossrulz said, contact NI if you have any questions.

Thanks, I've only been working on this tool for the last 14 years

So which private island will you be retiring to? 

MikaelH,

Sure I'm still answering questions. And I will still do bugg fixes and add new feature in my local copy and publish them on the forum.

Thanks for all of the hard work with GDS, you have officially contributed a substantial tool to LabVIEW!

Hi Brian, thanks for the post

But one thing I noticed recently was that LabVIEW crashes if you run the Create Child Class plugin in a class Project Window (right) as opposed to a standard Project Window (left)

...

Is this is what you are experiencing?

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.

jgcode, thanks for the info.  Unfortunately LabVIEW 2013 is crashing when I try to create a child class with your latest test build.

Very cool, I will be tuning in.

I am experiencing issues also.  LabVIEW crashes when using the Create Child class feature.

A few discussions related to identifying what hidden VIs are actually running:

http://lavag.org/topic/16660-how-to-get-actual-vi-execution-state/

https://decibel.ni.com/content/thread/18687

Some work-arounds are to use the Desktop Execution Trace Toolkit or LabVIEW Profile Tool.

When creating a lvlib there is no option to add an auto-populated folder to it. The only option is "Folder (Snapshot)".

Understood, but the auto-populating folders can automatically show new files that are not included within the lvlib.

I find out that the error was due to the fact that I manually renamed the lvlibp file and some dependencies were not found anymore.

 

Regarding the sourc lvlib I'm using to create the packed library, I have a single folder added as " Folder (Snapshot)". Is there any way to force a rescan of the folder and add new VIs to the lvlib ? At the moment, I have to remove the folder and all VIs from the lvlib and add them again.

I'm not quite sure what you are asking as all files within a lvlib will be shown.  However, you can use auto-populating folders to automatically add new files to a project.  

Packed project libraries include all dependencies except other packed project libraries and non-LabVIEW files (DLL, text files, ...).  So yes, vi.lib is included.

What does the error list say on the other computer?  Are you attempting to run on the same version of LabVIEW?

But there is good news... the plan -- and let me stress plan -- is to work on several debugging-related improvements for 2014, and I'm asking that some work be done to make this task manager work better. No promises, but I am making the request.

Please, please add a VI server call that properly reports which VI's are running!  (See thread here)

Last year they were posted at https://decibel.ni.com/content/groups/niweek-2012?view=documents

 

I don't see a niweek-2013 community yet, I guess we will get a notification in the next couple of weeks

Did you try the following:

https://decibel.ni.com/content/groups/niweek-2013

Thanks Mark, these videos are great.

I get the following page when I attempt to visit the code repository:

I haven't seen anything for session registration yet, but the sessions are listed:

Main Conference Content Page - http://www.ni.com/niweek/conference-content/

My NI Week Page - https://niweek2013.activeevents.com/connect/

Sessions - https://niweek2013.activeevents.com/connect/search.ww#loadSearch-searchPhrase=&searchType=session&tc=1&sortBy=&p=