LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
jyang72211

user.lib source control

Status: Declined

Any idea that has received less than 4 kudos within 4 years after posting will be automatically declined.

If you have a custom control or vi that you would like to access on your pallete, you need to save it into a folder called user.lib on your local drive.  If you have a team of developers and you would like them to have the same set of tools in their user.lib, it would be difficult, since the user.lib is maintained individually on their individual harddrives.  

 

It will be great if I can place a shortcut instead of a hardcopy of my custom vi into the user.lib.  The shortcut will point to a source control location, possibly a network drive.  Since it is no longer a hardcopy in the local user.lib folder but a shortcut, if a custom vi is updated, the shortcut will direct you to the latest copy. 

 

It will be so much better if I can tell LabVIEW where my custom vi or controls are, instead of having to save them in user.lib only.  The option will give much flexibility.

 

Yik 

 

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

Kudos and Accepted as Solution are welcome!
4 Comments
Spectre_Dave
Active Participant

Just add User.llb to Source Code Control.

Visualize the Solution

CLA

LabVIEW, LabVIEW FPGA
ibberger
Member

good idea, but what about linking complete folders (outside the user.lib directory) containing lib-VIs to the user.lib? I think that could come very handy, too ...

 

Maybe a possibility (like a list) in the files and directory settings, which allows the user to specify additional custom folders, which are treated as user.lib folders too, would be an option?

Knight of NI

You can like a palette item to any folder you want, so I don't understand what the issue is here. Just customize the palette and insert a subpalette that links to a directory. This would be part of the standard setup for a developer. Not to be blunt, but why should NI cater to the way your team is setup?

 

Personally, I think linking to a network folder (either via a shortcut or a direct palette item) is a bad idea.  One should not use a server as an extension of active development. The server should be used as a repository, and you should be updating local copies. What happens if someone "accidentally" overwrites the version on the server? "Oh, IT person! Need a restore from tape, please!"

Darren
Proven Zealot
Status changed to: Declined

Any idea that has received less than 4 kudos within 4 years after posting will be automatically declined.