Helix Core is now P4. Product user interfaces will be updated soon. Learn more >>

P4 for Eclipse Documentation | 2025.2

# Time-lapse View: Graphical annotation tool

Time-lapse View displays an interactive graphical representation of a file's history, showing when lines were added, changed, and deleted, who made the changes, and when the changes were made. Time-lapse view enables you to browse forward and back through changes dynamically, to locate changes of interest.

To display Time-lapse View, right-click the file of interest and choose Team>Time-lapse View. To move through revisions, use the slider. Time-lapse view is syntax-sensitive (C/C++, Java, and Ruby), enabling you to navigate file content using an outline view. To hide information that is not of interest, for example, to display only the changes to a single method, fold information using the +/- expander buttons.

The Time-lapse toolbar controls are shown in the following table:

Feature | Description
--- | ---
Scale | Specifies the unit used to display revisions: changelist The changes to files or stream specifications along with metadata, such as the list of changed files, their version numbers, the submitter of the changelist, and the submitter's description of the changes. A changelist is the unit of versioned work. number, date, or Perforce file revision number.
| Go to previous or next revision.
| Toggles display of integration history, to include content that was contributed by branch (noun) A set of related files that exist at a specific location in the P4 depot as a result of being copied to that location, as opposed to being added to that location. A group of related files is often referred to as a codeline. To associate code reviews in P4 Code Review (formerly Helix Swarm) with the projects they are part of, add the 'branch' paths in the P4 Code Reviewproject. (verb) To create a codeline by copying another codeline with the 'p4 integrate', 'p4 copy', or 'p4 populate' command. and merge 1. To create new files from existing files, preserving their history when branching. 2. To propagate changes from one set of files to another. 3. The process of combining the contents of two conflicting file revisions into a single file, typically using a merge tool, such as P4 Merge. operations as well as edits.
| Toggles display of information from the changelist in which the currently-selected revision was submitted.
| Toggles the display of action badges under the slider. The badges indicate the action (add, edit, or delete, for example) that was performed on the file in the corresponding changelist (or date or file revision, depending on the scale you select for the slider).
| Displays color coding to indicate how recently a change was entered, select Display Text Aging from the dropdown list. The darker the shading, the more recent the change. The default Most Recent and Least Recent colors can be changed from the dropdown list.
| Specifies how line endings and whitespace are treated to determine differences. Select how you want line endings and whitespace treated from the dropdown list.
| Toggles display of the user that made the change.
| Toggles the display of the range of revisions that include each line.
| Enable/disable folding, which enables you to show or hide chunks of text. Only available for certain file types
| For each chunk, display decorations under the slider indicating the status of the chunk in the corresponding revision.
| Reduce the increments under the slider by displaying only revisions that affect the currently-selected chunk.
| Link/unlink the selection in the outline view to the slider. When linked, the focus remains on the selected chunk when you use the slider to browse revisions.

Your search for returned results