LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Class locked (not loaded) - how to load it?

Solved!
Go to solution

Hello,

I have a project with AF actors and inside of one of the actors' lvlib there is a class that says it is not loaded. So in the right click menu of the class i click "Load" - this opens the class in a new project window but it stays not loaded in the original one. I have no idea how else i can load that class neither what is causing the lock actually.. Please someone help me.

 

Clipboard03.png

0 Kudos
Message 1 of 7
(11,255 Views)

Locked with a password perhaps?

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 2 of 7
(11,234 Views)

Hi Ben,

no the class is not locked with password

 

.. i tried to move the classes on disk, then reopen the project -after that i was able to remove the classes from the lvlib (as lv could not find them) and then i could re-add one of them without any problems, but the other not yet..

0 Kudos
Message 3 of 7
(11,211 Views)
Solution
Accepted by topic author ravyh

I eventually resolved this by deleting the instances of this class in other VIs -then once i did Edit -> Undo and labview [magically] asked me if i want to remove this class from it's owning library (even though the library didn't show the class as its member in project viewer) so i 'removed' it and everything is fine now.

Message 4 of 7
(11,202 Views)

@ravyh wrote:

I eventually resolved this by deleting the instances of this class in other VIs -then once i did Edit -> Undo and labview [magically] asked me if i want to remove this class from it's owning library (even though the library didn't show the class as its member in project viewer) so i 'removed' it and everything is fine now.


Speculating...

 

Libraries (and classes) have a XML file that contains info about them and ownership etc. Provided they are moved using the functions in the Project, they files get updated as things are moved. Now if things get moved OUTSIDE of LabVIEW, then we can run into odd situation where the files of the libraries are inconsistent with each other. Try to do all of the moving a shuffling INSIDE of LabVIEW to avoid those types of issues. Not saying that was the situation for this thread. Only mentioning that that final message sounded familiar.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 5 of 7
(11,193 Views)

@Ben wrote:

Try to do all of the moving a shuffling INSIDE of LabVIEW to avoid those types of issues.

For the most convenience, use the "Files" view in the project.  This will show the directory structure on disk.  You can then just drag your files to where you want them and then deal with the warning message about all of the VIs, etc that will be updated because of this move.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 6 of 7
(11,187 Views)

I ran into the same problem.  It occurred when I accidentally created accessors with the same name in the same class.  That crashed LabVIEW and then recover crashed.  I was able to fix it by opening my .lvclass in notepad++ and modifying the XML code.  I renamed the duplicate VI to what I wanted it to be.  Thanks to Ben for planting the seed that .lvclass is XML based!!!

0 Kudos
Message 7 of 7
(11,137 Views)