Source Code Control Options Dialog Box

The Source Code Control button in the Environment and Edit Project dialog boxes opens the Source Code Control Options dialog box, where you can configure LabWindows/CVI to work with a third-party source control provider.

To configure source code control settings for the LabWindows/CVI environment, select the Source Code Control button in the Environment dialog box. Select Options»Environment to access the Environment dialog box.

To configure source code control settings for an individual project, select the Source Code Control button in the Edit Project dialog box. Select Edit»Project to access the Edit Project dialog box.

This dialog box contains the following options:

  • Use project Source Code Control settings—Enable this option to specify source code control settings for the currently loaded project. This option is available only when you access the Source Code Control Options dialog box the through the Edit Project dialog box.
  • Provider—The name of the source code control system that contains the source code control project.
  • Project—The name of the source code control project.
  • Select—Attach an existing source code control system project. To select a provider, highlight its name and click OK to confirm the selection. To exit the dialog box without selecting a provider, click Cancel.
  • Perform same actions for .h file as for .uir file—Because LabWindows/CVI generates a header file for the .uir file each time you save the .uir file, it is a good idea to perform the same source code actions on the header file as you perform on the .uir file.
    • Never—When you perform a source code control action, LabWindows/CVI does not perform the same action on the header file and on the associated .uir file.
    • Ask—When you perform a source code control action, LabWindows/CVI asks if you want to perform the same action on the header file and on the associated .uir file.
    • Always—When you perform a source code control action, LabWindows/CVI automatically performs the same action on the header file and on the associated .uir file.
  • Perform same actions for .cds file as for .prj file—Because LabWindows/CVI saves the .cds file when you unload a workspace, it is a good idea to perform the same source code actions on the .cds file as you perform on the .prj file.
    • Never—When you perform a source code control action, LabWindows/CVI does not perform the same action on the .cds file and on the associated .prj file.
    • Ask—When you perform a source code control action, LabWindows/CVI asks if you want to perform the same action on the .cds file and on the associated .prj file.
    • Always—When you perform a source code control action, LabWindows/CVI automatically performs the same action on the .cds file and on the associated .prj file.
  • Suppress CVI Error Message dialog—Some source code control systems display their own dialog boxes when errors occur during a source code control operation. Enabling this option suppresses all LabWindows/CVI error dialog boxes displayed when an error is reported by the source code control system.
  • Always show confirmation dialog—Displays a dialog box where you can confirm your source code control actions.
  • Use default comment—Enable this option if you do not want to be prompted for a comment when you check in or add files to a source code control project. Enter the comment that you want LabWindows/CVI to pass to the source code control system.
  • Use default username—You can change your username by enabling this option and entering a new name.
  • Advanced—Access advanced options provided by your source code control system. If your source code control system does not provide advanced options, this control is dimmed.

WAS THIS ARTICLE HELPFUL?

Not Helpful