Leaderboard

I mean if you can’t service the queue as fast as elements are added, then you’ll eventually run out of memory. — James PS, if you recall this conversation we had, one can use a timeout in a way that is guaranteed to execute the desired code on time

You can set the INI variable and restart LabVIEW using two Invoke Nodes. You will have to confirm "Quit will abort all running VIs" and it should start back up with the correct setting. (LV 2012)

Ton, I think 2Ls wants the DVR to reference a different or rather extended collection of data that the parent object has. For 2Ls, it is important to remember that a DVR is a reference to specifically typed data. There is no way to make a DVR reference something that it isn't. So, the DVR does not really buy much here. A suggestion for 2Ls... Perhaps the private data in the parent can be an object itself, call it ObjectData.lvclass. Now when a child gets Initialized, it can call the parents 'Write ObjectData' accessor with a class derived from ObjectData.lvclass. This derived class has the extra information needed. If you still need to use a DVR, perhaps supply a 'New Data Value Reference' node with ObjectData.lvclass or one of it's derived classes. Now 'parent' methods can get access to the what the child implementation created. Is that what you were thinking 2Ls? Kurt