Version control options

Activate this checkbox to change your project to a version-controlled project. A version-controlled project creates a working copy folder "ProjectName.vcf" (vcf = version-controlled folder) in the same file path where your project is stored. This working copy can then be introduced into a project repository containing the complete project history.

The conventional project is completely split into a "mirror" of the project, called "working copy" that is stored in a separate version-controlled folder. The working copy contains the same configuration data as the project file in general, but the working copy contains a detailed object structure with the granularity known from the navigator and mostly human-readable files in contrast to the project file. This structure of folders and files is created to allow version control and multi-user development.

Moreover, working copy and project are automatically kept in sync without visible user interaction. Any save of a changed object in Control FPWIN Pro7 is reflected in an instant update of the corresponding object’s file in the working copy. If the user updates his local working copy with the latest changes stored in the project repository, Control FPWIN Pro7 (normally) reflects the latest changes automatically in the open project.

The working copy is designated to be imported once and for all into a global project repository for this project (to be done manually outside of Control FPWIN Pro7). As the only original ("official") source for this project, this repository contains all revisions, changes, change information and dates to be used by all cooperative users of this project. Last not least, the repository is the key to inspect, commit, update, merge, and revert (undo) any changes done to a working copy from every user's and all users' perspective.

Deactivating version control for an existing version-controlled project changes your project to a conventional project again. In this case, the working copy is not deleted automatically.