I am writing some classes with the new class type in Labview 8.2. I like them in general but I was wondering if they protect against tampering when multithreading.
For instance, in the past I have used a queue to store class data, so that only the function that is using the data has access and another call which accesses the same data must wait for the cluster to be put back into the queue. This nicely prevents one VI from editing the class data out from under another VI.
Where I see a problem is in using this new User Class paradigm in labview 8.2. If i want to be able to inherit things from one class to the next I need access to the private data of that parent class. That can be a pain if the private data from the parent class is a queue which only had a pointer to a cluster with my data. Then what will be the additional data in my daughter class? A second queue with the daughter's private information?
Does using one VI within a user class prevent another VI within the class from writing to the private data before the first VI exits? Is there a setting that would implement this behavior. I am having trouble getting any sort of details about the working of the class system.
Kevan -
