Disabled code still is listed in project dependancies

[viScience]

I have noticed that in my project, disabled code blocks in my top level vi for a cRIO target still are listed under that targets dependancies in the project tree.  It seems like this is a bug and can cause misleading investigations when you are searching for instances on a vi within your project.

[RavensFan]

I would say that it is probably not a bug, but expected behavior.  Since the VI still references the subVI, even though it isn't called, it is still a part of the project hierarchy.  There were also some recent discussions about the unused instances of polymorphic VI's and whether those instances should show up in the VI hierarchy.  Some of those arguments would probably apply.

[Ben]

---

@Ravens Fan wrote:

I would say that it is probably not a bug, but expected behavior.  Since the VI still references the subVI, even though it isn't called, it is still a part of the project hierarchy.  There were also some recent discussions about the unused instances of polymorphic VI's and whether those instances should show up in the VI hierarchy.  Some of those arguments would probably apply.

---

Case in point:

To do a "Source Distribution" you need all of the code so it must be included. An earlier version of LV had a bug where it did skip code that was disabled. This has since been corrected.

Ben

[viScience]

Ok, point taken.  Maybe the problem is in the find callers behaviour, perhaps there should be an option to skip disabled code.