01-05-2016 03:32 AM
I am looking for a while and didn't find an answer. is there a possibility of hiding vi-s in Project/Dependencies which are in Disabled structures and so are not executing?
01-05-2016 03:51 AM - edited 01-05-2016 03:52 AM
No - the dependencies shows all VIs which are in memory which are not explicitly included in the project. As VIs in a diagram disable structure are loaded into memory (even though they are not executed) when the VI/project is opened, they will appear in the dependencies. The only way to remove them would be to remove them from the block diagram entirely (but they do get compiled out when building executables).
01-05-2016 06:03 AM
Thank you for answer. It would be nice if there would be a checkbox to exclude not used vi-s under dependencies.
This would be useful when you work on a large similar project 90% the same for checking that you referenced new vi-s correctly. For example first save master vi as new name in new project/folder and then use structure disable just for info what is needed to do and how was done. Then under project/dependencies you can find if some needed vi is still looking to old project and needs to be saved to new project with new name. I got a lesson that it is importand to not use the same vi names for different but similar vi-s in different projects.
01-05-2016 07:42 AM
In that case - you should use the 'files' tab of the project window as it will tell you the locations of the files on disk so you can easily see if it is pointing to the wrong file. lvlibs can help with the namespacing and VI packages help with sharing re-use libraries between projects 🙂