The Perforce SCC system performs file operations by sending the request through the Perforce command line interface. The commands are sent from the directory in which your file is saved. Most of the menu commands execute several steps, described below, to create a simple interface to Perforce.
Note You have the option to leave VIs in LLBs. However, all source code control operations on a VI are performed on the LLB containing that VI, not on the VI itself.
Get Latest VersionCopies the latest version to your local directory and reverts the VI. If the file was originally checked out, it is checked back out after the copy. Any changes that you made to the VI are lost.
Check InSaves the VI, prompts you to enter a Change Description, reopens the file in a new changelist, submits that changelist, and reverts the VI. Submitting a changelist copies the local file to the server. You must have the latest version of the file for this operation to succeed.
Check OutIf you do not have the latest version, checking out a file copies the latest revision to your local directory before opening it in the default changelist. Unless you did not select Only one client can check out a file checkbox in the Select your Perforce configuration options dialog box, the file must not be opened by another user. In either case, the file cannot be locked. The file type is binary or binary+w (always writeable on client) depending on the setting you selected for Files on client are read only when configuring Perforce. If you selected Checking out also locks file, the file is locked after it is opened, and the VI is reverted.
Undo Check OutRemoves the file from the default changelist, copies the server version to your local directory, and reverts the VI. This command uses Perforce's p4 revert, which copies the server version to which you last synced. Any changes that you made to the VI are lost.
Add to SCCSaves the VI, opens it in the default changelist as binary or binary+w (always writeable on client) depending on the options you selected when configuring Perforce, reopens the file in a new changelist, submits that changelist with the comment, adds the VI to SCC, and reverts the VI. You must save the VI within the root directory structure designated by the client specification.
Remove from SCCOpens the file for delete, reopens the file in a new changelist, submits that changelist, and closes the VI. This command changes the file status, or head action, to delete and deletes the file from your local directory. Perforce retains all previous versions of the file.
Show HistoryDisplays the revision history provided by Perforce.
Compare FilesCopies the head revision from Perforce to your temporary directory as head.filename and compares the files using LabVIEW. The temporary file is deleted from your temp directory, but the file remains in memory.
PropertiesDisplays the properties of the file Perforce maintains. Refer to the Perforce Software, Inc. Web site for terminology.