Hi! Looking at the documentation online for the Lock Step, it appears that there are a few properties that only exist if a thread is locked. Lock Step documentation here shows that the Step.Result.TimeoutOccurred property only exists if the thread is locked.
Thanks for the answer but this is only valid for the lock step. If for instance the lock has been done on a subsequence call and I need to figure out inside the sub sequence if the sequence is locked or a previous lock step has locked the thread this information is not available.
Normally my customers use batchmodel for testing and (for some different reasons) needs to lock threads. Creating functions (typically a sub sequences or just a VI) for my customer i need, in some cases, to know if the thread is locked.
The customer has different options to lock the thread:
- "Lock" step
- "Use Lock to Allow....." in "Synchronization" under step properties
(- "Batch Synchronization -serial" in "Synchronization" under step properties)
I can't use the suggestion by Chantastic! because I am not in the lock step and if the customer use the "Lock" in the synchronization tab the parameters does not exist.
Hope this answered your question Doug?
Threads themselves are not locked, but rather they own locks and they can own more than one. Why do you need to know if the thread owns a lock?