LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Naming conventions

We just had a post conflict. I think I answered your question while you were asking it.

 

One point to clarify...

 

Libraries as in

 

Project >>> Create new >>> Library

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 11 of 19
(1,156 Views)

We are!

------------------------------------------------------------------

Kudos and Accepted as Solution are welcome!
Message 12 of 19
(1,161 Views)

ok.  so you used the 3 lvproj and 3 lvlib option?  For each lvlib, you wouuld have a lvproj?

------------------------------------------------------------------

Kudos and Accepted as Solution are welcome!
0 Kudos
Message 13 of 19
(1,150 Views)

I understand that the name of the lvlib will be part of the name scope.  Is the project name also part of the name scope?  

------------------------------------------------------------------

Kudos and Accepted as Solution are welcome!
0 Kudos
Message 14 of 19
(1,143 Views)

Capture.PNG

 

There is an ini option to show FQN's it the title bar

the FQN is  Library.lvlib:Member.ext Pane on Project Name.lvproj/Target

 

This completely eliminates naming conflicts! (unless I create another vi of the same name in the same library in the same target in the same project but that would be really silly)


"Should be" isn't "Is" -Jay
Message 15 of 19
(1,138 Views)

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. 

------------------------------------------------------------------

Kudos and Accepted as Solution are welcome!
0 Kudos
Message 16 of 19
(1,130 Views)
Quote

don't do that. Open probed members in the project so changes are saved in the project. Opening random prom 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.

"Should be" isn't "Is" -Jay
Message 17 of 19
(1,125 Views)

What probed member did you refer to?  The quote didn't show up, so I don't know what were you responding to.

------------------------------------------------------------------

Kudos and Accepted as Solution are welcome!
0 Kudos
Message 18 of 19
(1,092 Views)
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
Message 19 of 19
(1,083 Views)