05-08-2012 05:07 AM
I've run into some particularly weird behavior of LabVIEW 2011 SP1:
I've tried to summarize this in the picture below:
So I'm not entirely sure what's causing this behavior:
Feel free to contact me if the actual files are needed for further investigation.
Thanks!
05-08-2012 08:38 AM
Could you please post an image of the code containing th static reference?
Curious,
Ben
05-08-2012 08:57 AM
Sure 🙂 It's nothing special:
Note that I've used similar code for years all over the place, but this is the first time I've encountered this issue.
05-21-2012 08:32 AM
Hello onnodb,
I do not have explanations for such a behaviour at the moment.
Perhaps you can post the actual project in order for me to reproduce the issue and see what is going on?
Thanks!
05-22-2012 03:06 AM
Hello Cédric,
Thanks for your reply! It's much appreciated.
Would it be possible to send a snapshot of the code by email? It's a relatively big project that's still under development for a scientific research group, so I'd rather not have the code publicly available at this point.
Best regards,
Onno
06-14-2012 08:57 AM
Hello,
This behaviour is actually caused by the auto-populating folder feature. If you put that feature off, the library does not appear locked anymore.
The issue has been reported to the developpers and should be corrected in a further revision.
@ Onno: I just sum up here our discussion to make this post complete, nothing new for you.
06-14-2012 10:03 AM
@cedhoc wrote:
Hello,
This behaviour is actually caused by the auto-populating folder feature. If you put that feature off, the library does not appear locked anymore.
The issue has been reported to the developpers and should be corrected in a further revision.
@ Onno: I just sum up here our discussion to make this post complete, nothing new for you.
Please post the CAR number so we can check for it being fixed.
Than kyou,
Ben
06-29-2012 04:12 AM
Hey,
Actually, there are more than one CAR related to the auto populating feature opened at the moment 🙂
Ealier in the development of his project, Onno ran into some corruption of his project (for reasons only him can give you). He thought he had resolved -most of- them. Thus, the locked library issue he still have at the moment is probably a consequence of a previous corruption. Because of that, I cannot give you a precise CAR reference, but for sure, the R&D is aware of some issue with the auto-populating folder. This one (CAR#347498) is probably intersting to follow though.
08-04-2015 07:20 AM
I just ran into this problem and thankfully, was able to fix it in my case. I'm using LabVIEW 2011 with classes and autopopulating folders.
1. I was able to open the class by itself and it wasn't locked.
2. When I opened the project, the class became locked.
3. After looking through the vis in the project I found one vi that was formerly part of the class but I had removed from the class.
4. The vi itself was set to be part of the class even though it shouldn't have been. I deleted the offending vi and the class was no longer locked. I'm sure you can also just save the vi instead of deleting it. However, I didn't try that approach because I didn't need the vi in this case.
Hope this helps!