11-28-2012 04:25 PM
We have multiple developers working on the same project and I want to avoid 2 developers editing the same vi at the same time. Is there a way, as in Excel, to make a vi "read-only" to others as soon as it's opened by a developer?
Solved! Go to Solution.
11-28-2012 04:28 PM
Yes, Thats called a source code control repository. In most cases code that in checked into the repository is marked "Read Only" and only 1 person can obtain a lock at a given time. There is an ini token to treat read only code as locked.
11-28-2012 05:21 PM
Just to reiterate. If you are working with groups, you have to have a good source control setup. This is mostly for the situation you just described. Even if you are doing development on your own, you should be using source control so you can go back after making stupid mistakes.
11-28-2012 06:32 PM
Thank you, but so far I've been advised to use "source code control repository" and "source code setup". It sounds good but where do these tools come from? How do I establish a "source code setup"? Is that something offered by NI? Can you narrow the field of search just a bit?
11-28-2012 07:59 PM
11-28-2012 09:32 PM
Thank you VERY much. That's JUST what I needed to know.
12-18-2012 07:06 AM
I've been reading all the suggested material, and thank you all for that direction, but I'm not finding what I need to know. These third party control programs are overkill for our needs. And in Tortoise I didn't find the fundamental tool that I need, which is the Excel-type warning to developer2 that developer1 has the vi open already. THAT is mainly what I'm looking for w/o all the extra overhead. Maybe TortoiseSVN is the tool I need, but instead of reading pages and pages of fine print I'd like to talk to someone familiar with it. Any suggestions?
12-19-2012 02:56 PM
It would be best if you posted your question in a new thread, as this one has been marked as answered and people are not likely to look at it.
That said:
Labview does not prompt the user when opening a read only file. It does generate an error when trying to save however.
Excel immediately asks the user how to proceed when opening a read only file. It also has a semaphore like operation where it changes the file properties when it has a file open so other systems cannot edit it.
Tortoise makes it easy to implement version control and a little easier for multiple people to edit different files of the source code. As far as I know it doesn't quite implement what you are looking for though.
Again, if you want more assistance on this please post in a new thread.
12-20-2012 06:35 AM
12-20-2012 10:51 AM
I just found this out as well, which should help a lot for editing things:
There is an option under Toos » Options » Environment » Turn on Treat read-only VIs as locked that will change how LabVIEW opens a VI when it is read only!