Repost without the darn dumb-phone
@jyang72211 wrote:
i tried that. It seems like lvproj is not a part of the name. I tried the following: I created two folders: aaa and bbb. Inside aaa, I have aaa.vi, aaa.lvlib, and aaa.lvproj. Inside bbb, I have aaa.vi, aaa.lvlib, but bbb.lvproj. When I open aaa.vi from the two different locations seperately, there is a name conflict. See attached. It seems like only lvlib adds to the naming resolution.
Don't do that! Open project members in the project so changes are saved in the project. Opening random project members is like going out to the parking lot and driving home in whatever car looks good today. If you do that too often the owners get frustrated.
This is because projects know their membership (the names of the members are in the *lvproj file) Open one with internet explorer! it is really just an XML file. The members do not know anything about the project though. Kind of like your relationship with your car. You want to keep a good idea about where it is and who is doing what with it right? But the car doesn't care who puts in a key and drives it away.
Library members, on the other hand, DO know what library (or Packed Project Library) they belong to and even decorate their names so the world can see. This does more to prevent name space conflicts than just being in a project since the member "remembers" its owner is a library even if the library is not in memory.
Projects- Libraries are good for you. And if properly named change the way vi's are named! Ben's FPGA_Read AI.vi could very well be"
FPGA.lvlib:Read AI on Client Product.lvproj ! much nicer and you don't look like a txt hack!
"Should be" isn't "Is" -Jay
