Actor Framework Discussions

Showing results for 
Search instead for 
Did you mean: 

Why do messages stay in Dependencies when removing them from project?

Go to solution

I sometimes remove a message and its corresponding public method when I decide it's no longer needed. However, the message ends up in the "Items in Memory" folder and won't go away until I quit the project and my project is broken until doing so despite removing all references to the message and public method.


Is there a way to remove them from the project completely without quitting and restarting my project?

0 Kudos
Message 1 of 3

I am not aware of a different way. Yet, I have to admit, that I don't have a problem closing/ reopening since it makes sure the project has been loaded correctly. IMHO, just a minor nuisance.

Programming languages don't create bad code, programmers create bad code....
Message 2 of 3
Accepted by topic author BillMe
04-14-2019 11:21 PM

Classes have to stay in memory if there might be objects of that class in parent-class controls.  Otherwise LabVIEW might crash on trying to access an object whose class has been unloaded. Unfortunately there is no way to get around this that I know of other than closing everything.

Message 3 of 3