The Advanced Properties tab may be accessed from two locations:
| · | Global Mode - When accessed from the Project Properties dialog box by the project administrator, the settings are applied globally and will affect all the users of the project.
|
| · | Workstation Mode - Every user may access the tab from the Workstation Properties dialog box and set the desired options which affect the local workstation only.
|
|
You can always use the following buttons to reset to the system defaults:
| · | Inherit All - When clicked in Global Mode, settings are inherited from the master project (for top-level projects, the settings are inherited from the system defaults). When working in Workstation Mode, settings are inherited from the project's global settings, as defined by the project administrator.
|
| · | Default - When clicked in Global Mode, all defaults settings provided by ComponentSoftware will be applied. This option is disabled in Workstation Mode.
|
|
|
Document Explorer
|
|
| Calculate status on open
|
| · | True – Files statuses are updated when the Document Explorer is opened. This ensures that all files' statuses are up to date.
|
| · | False – You must take an action in order to update the project files status, e.g. click on F5 or right-click on the selected files. Select this option when working with very large projects or with co-located projects.
|
|
|
| Project select threshold
|
| Launching the Document Explorer with large projects might be time consuming. If the project contains more files than the number indicated in the Project select threshold property, the Project Select dialog will open giving the user the option to choose a sub-project.
|
|
|
| Update status automatically
|
| · | True – The Document Explorer updates the files status automatically whenever it becomes the active window. This may slow down the Document Explorer response when working with large projects.
|
| · | False – You must take an action in order to update the project files status, e.g. click on F5 or right-click on the selected files.
|
|
|
| Recalculate Status on scan
|
| · | True – Recalculate status of all files when the Project | Scan new files command is executed. This ensures the status matches the repository status.
|
| · | False – Status is calculated by using information cached on the local workstation. You may safely select this option when working with large or co-located projects.
|
| Check-in scans for new file
|
| · | True - Scan the work folders for new files when the Project | Check-in command is executed.
|
| · | False – Check-in modified files only. Select this option for faster check-in operations.
|
File Handling
|
|
| Use shared work folder
|
| · | None – Normally, the working files should reside on your local drive or on a private server drive (and not on a shared server drive). This method provides each user a "sandbox" where changes can be performed and tested. Thereafter, the changes are committed to the repository. Please follow the workgroup tutorial of the online-help to get familiar with this concept.
|
| · | NTFS Permissions – Select this option for environments where all users share a single work folder defined by the project manager. Selecting this switch instructs CS-RCS to give the proper interpretation to file updates scenarios. CS-RCS uses NTFS security features to grant edit permission solely to the user that checked-out the document. Note that some Windows file-servers do not support these security features; on these servers, all users might be able to edit an exclusively locked document. For more details, see the FAQ: How should I define a shared work folder on the server?
|
| · | Windows Permissions – Select this option for environments where all users share a single work folder defined by the project manager. Selecting this switch instructs CS-RCS to give the proper interpretation to file updates scenarios. CS-RCS will not use NTFS security features and as a result, all users will be able to edit an exclusively locked document.
|
|
|
| Define new file parameters
|
| · | True – Whenever a new file is added to CS-RCS, you will get a dialog box enabling you to configure various parameters of the newly added file including initial revision, lock status, etc.
|
| · | False – CS-RCS will use the default parameters for the new file.
|
|
|
| Specify symbolic name on check-in
|
| · | True – Enables the user to define a symbolic name for a file revision when checking-in or adding a new file to the project.
|
| · | False – This option is disabled by default as symbolic names are supported for compatibility reasons only. You should normally use the CS-RCS Milestone features, which provide superior functionality.
|
|
|
| Use Unix line break
|
| · | True – Create work files using the UNIX line-break sequence. This feature is useful if you wish to use UNIX tools to process the work files.
|
| · | False – Create normal windows work files.
|
|
|
| Exclusive locks on binary files
|
| · | True – Binary files always use exclusive locking, even on CVS-mode projects. This prevents merge conflicts which are hard to resolve on binary files.
|
| · | False – Binary files use the working mode of the project, same way as text files.
|
|
|
| Check-Out Time Mode
|
| · | Current Time – Create work files using current time (time of check-out or update operation).
|
| · | Archive Time – Create work files using the time of the checked-in revisions. This is useful if you want to compare the work folder to another folder. However, it should be used with caution since it may "confuse" compilers or project build tools (i.e., the "make" utility).
|
|
|
| Check-In Time Mode
|
| · | Current Time – Check-in new revisions using the current time. This feature helps to group related changes.
|
| · | Archive Time – Check-in new revisions using the time the work file was last modified. This is useful while checking-in changes performed by third-party, or when building an RCS database from backups of old releases.
|
|
|
| Create backup files
|
| · | True – Create backup files (.Bak extension) when the checked-in revision differs from the original revision. This may happen when adding binary files to the repository while the file-type is mistakenly defined as text.
|
| · | False – Never create backup files.
|
|
|
|
|
| Keyword expansion
|
| · | True – Expand all RCS keywords during check-in and check-out.
|
| · | False – Expand RCS keywords during Retrieve revision command only. As RCS keywords are normally ignored during normal development, this feature may improve performance on RCS commands and product builds. Note: Files containing the keyword $Log, will have all keywords expanded regardless to the state of this option.
|
|
|
| Scan keywords
|
| CS-RCS scans for RCS keywords on the first lines only. Set this number to the minimum to improve performance. This parameter is ignored when the Expand keywords parameter is set to False.
|
|
|
| Local Time Keyword expansion
|
| · | True – Display local time in expanded RCS keywords.
|
| · | False – Display UTC in expanded RCS keywords. This is useful when users are located in different time zones.
|
|
|
| Update MS-Office tags
|
| · | True – Update tags in MS-Word and MS-Excel documents when checking-in a new revision.
|
| · | False – Don't update. Disable this feature for faster check-in or on workstations that do not have MS-Office installed.
|
|
|
| Update OpenOffice Writer tags
|
| · | True – Update tags in OpenOffice Writer documents (odt and sxw) when checking-in a new revision.
|
| · | False – Don't update. Disable this feature for faster check-in.
|
|
|
|
|
| Use local cache
|
| · | True – Store repository information locally. This improves performance significantly.
|
| · | False – Select this option to save space (recommended for unused projects only).
|
|
|
| Refresh file status
|
| CS-RCS is optimized to cache the repository status for certain amount of seconds. Increase this number on slow connections to improve performance.
|
|
|
| Windows Explorer integration
|
| · | True – Enable access to project files from the Windows explorer.
|
| · | False – Do not access from the Windows Explorer. Choose this option for projects with slow connection to the repository.
|
|
|
| Use global directory
|
| · | True – The list of files in the project is stored on the project repository.
|
| · | False – Every workstation calculates the file list. You must execute Project | Scan new files to detect new files added to the project.
|
|
|
| Optimized lock/unlock
|
| · | True – Use optimized method to lock & unlock files.
|
| · | False – Use traditional GNU method. Disable this feature on projects that are accessed by GNU RCS or GNU CVS.
|
|
|
|
|
| Get file name from title
|
| · | True – Display the file title instead of file name in the Document Explorer window. This feature is used in rare situations only.
|
| · | False – Display file names normally.
|
|
|