Lock VI.Lib User.Lib VIs

Question

So recently I found myself accidentally editing some VIs in my user.lib.  They were some reuse VIs that I was making a copy of to edit, and instead of editing my copy I edited the original.  Because of this I went through and made all reuse VIs locked but with no password to help others from making the same mistake.  
So now when the reuse library is installed and a user opens, they will need to unlock it before editing.  Not a big deal and it isn't hiding anything behind a password.  But it got me thinking, should NI do something similar with their VIs?  Is this one step to help users from editing these files?  Is it not necessary?  And can anyone think of any draw backs to mass locking a reuse library.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Answer 1

Jeff·Þ·Bohrer wrote:
The simpler solution is to make them read only and hit the ini option to treat them as locked.  In Fact, your SCC does this already.  Unless you check out the library you intend to edit, the files will be read only.  That ini setting is one of my favorites and has saved me many headaches.
Depending on where I am- vi.llb gets set to read only and some user's are handed ini files that contain the treat read only vis as locked flag set and told to never ever change it or "Pain there will be pain!" and I've been known to have a vi.lib back-up on a thumb drive on my key-ring! (Some users just have to learn the hard way!)
Onto the next observation: if you are making a copy of a reuse vi to edit you probably saved it with the wrong extension in the wrong location.  it belongs somewhere in templates as a vit.  
I didn't fully explain my situation.  This VI is not the kind of thing that I would want a VIT for.  It was a utility VI that I wanted to see if I could improve so I wanted to save a copy elsewhere, as a new VI then edit it and compare the performance to the one in the user.lib which I expected to be untouched.
I started by setting all files to read only.  This is faster then having to open a reference, edit, and resave the VI.  But as soon as installed the reuse library on a new version of LabVIEW it had to mass compile, which it had problems doing since I couldn't resave the file.  Part of the package making process involves opening references to update description and such so I already have the reference open.  Adding the Lock to the VIs I wanted didn't seem to add much overhead.
Thanks for the link to the Idea exchange I did a search on locking VIs but that didn't come up.  The discussion is very interesting since I use Save All quite often.
Edit: Oh geez.  I event commented in that idea exchange shows how much I remember.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.