Apologies if this is the wrong place for this post, but I'm quite puzzled by something I'm seeing. I expected a test that I just ran to potentially reveal a limitation of installing packages in the global AND virtual environments, but it is in fact working as I would like, and I would love to understand why this is possible... so if anyone will humor me, here goes:
Here's my situation:
I use the PaneRelief toolkit, so I have that installed in my LV2020 environment (globally).
PaneRelief depends on a number of other packages, like Panel Manager, so I also have to install those into the LV2020 environment.
I added a breakpoint to the Panel Manager code in the global environment (you'll see why)
I want to use Panel Manager in my project too, so I added the package to the my virtual environment.
I wrote a vi that uses the Panel Manager vi's from my virtual environment, so I know these vi's were pulled into memory. I confirmed by checking my lvproj's dependencies
While this vi is open, I use the quickdrop shortcut to launch PaneRelief.. I expected it to load its Panel Manager dependencies from the virtual environment since those were already in memory.
However, and much to my delight, it did in fact hit the breakpoint, indicating that PaneRelief loaded its Panel Manager dependencies from LV2020 vi.lib.
I guess I'm curious why this did not cause a conflict or load from the incorrect location - I'm normally used to seeing LabVIEW always defer to a vi in memory with the correct name rather than load from file, but that doesn't appear to be what I'm seeing.
Thank you!
Steven