A view specifies the data shown in the CXInsight main window. Use the view bar to save and switch between views rapidly.

Some common uses of views are;-

• Provide shortcuts to your projects or workspaces.
• Show a list of checked out files.
• Extend revision lists to include ancestor files.
• Reveal deleted files.
• View the database in a historic state.

Creating a view.

There are several methods to create a new view;-

1) Menu option Tools, View.
2) Right click the View Bar and select "New View".
3) Drag an entry in the tree view to the View Bar.

Options 1 and 2 give the dialog shown below. Specify the details you require.
Option 3 creates a view based on current settings, rooted at the dragged folder.

Newly created views are added to the View Bar.

The active view.

At any time one view only will be active for an instance of the CodeMatrix main window, and this view defines the set of files and revisions that will be shown in the tree and list views. The active view is the most recently created view or the most recently selected from the view bar. The name of the active view is displayed in the area above the Folder View.

View options.

The various options on the view dialog are described below.

Name. A view must have a name to identify it, this name need not be unique.

Look in. Specifies the root folder for the view. Only file revisions in this folder and optionally its descendants are shown when the view is active. Use the adjacent Browse button to change this setting.

Named. A specific file name or pattern may be entered. When the view is active only revisions of file whose names match the name or pattern are shown. A pattern may use the characters ? or * to represent any character or characters respectively. E.g. *.html will include only revisions of files with names that end with ".html".

Change. Each update to the CodeMatrix database is assigned a unique change reference number. Use this field to include revisions for a range of changes. Use the ">" symbol to define a change range as shown in the examples below.

Specifying a single change number is useful to view the database in the state that existed at the point of that change.

Label / attribute / user / role. Use this field to select revisions that;

• Have been associated with a specified  label.
• Are for files that have been associated with a specified attribute.
• Were created by a specified user.
• Were created by a user having a specified role.

Use the adjacent Browse button to select the required label, attribute, user, or role.

Revision date range.  Use this field to include revisions created in a specified date/time range. Use the From and To buttons to specify the date/time range. Date time ranges are shown in the following format.

Include subfolders. Select this option to include file revisions beneath the "look in" folder.

Show branch ancestors. If selected the revision history is extended to include revisions from which branches were taken.

Show delete revisions. Enable the inclusion of delete revisions.

Checked out only. Files which are not checked out are excluded.

Show descendants. This advanced option includes files from subfolders to be shown in the list view. It is commonly used in conjunction with the checked out only option to give a flat list of all checked out files in a workspace.