04-30-2012 09:58 AM
When you already have a file/project open in LabVIEW and it is set to read only because you haven't checked it out, you can go into SCC and do a checkout then save the file immediately. The issue with this is, if your local copy doesn't match the copy in SCC, you will probably be overwriting changes. Sometimes this is convenient because if you have ever edited a MS Word file and then gone to save and it won't let you because it was opened as read-only...then that sucks because you either lose your work, or have to do a copy of the entire word file->close the program->re-open as writable, then paste. This can be avoided with the "LabVIEW way", but the "MS Word" way seems much safer because it forces you to conscioiusly make the file writable (by either checking it out or manually write clicking and changing to writable) BEFORE opening it. I just wanted people's opinions on how LabVIEW handles this, and if there would be a better way.
04-30-2012 01:15 PM
What SCC package are you using? With Subversion the whole matter becomes a non-issue since conflicts are resolved when you commit back to the repository.
Mike...
04-30-2012 05:07 PM
VSS ![]()
04-30-2012 05:44 PM
Are you using any source control integration with LabVIEW? At least with Perforce, and I assume with other SCC providers, when you check out the file within the LabVIEW development environment it will ask you if you would like to get the latest version and if you do so, it will reload the VI after retrieving the latest version. I believe there is a source control provider for VSS that LabVIEW can use. Lower-cost editions of LabVIEW do not include source control integration so you may not have access to it.