Configuring P4V Preferences

To configure settings for P4V, go to Edit > Preferences... (Windows) or P4V > Preferences... (Mac). The Preferences dialog includes the following configuration pages:

Click Apply to save your changes. Click OK to save your changes and exit the dialog.

Note

Local versus centralized preferences: Many P4V preferences can be defined or disabled centrally using the Perforce service. For example, an administrator can disable the Labels tab centrally, and you cannot override this setting in your local P4V preferences to make the Labels tab available. These centralized settings are specific to a Perforce service, so if you switch your connection to a different Perforce service during a P4V session, you may see different behaviors after you open the new connection. For example, if Perforce service A has enabled the Labels tab and Perforce service B has disabled it, the Labels tab will become unavailable when you switch your connection from service A to service B. Note also that there are performance-related preferences (such as those on the Server Data page) that can be set centrally using the Perforce service. If these centrally-set performance preferences differ from your local preferences, your local settings will continue to appear in the Preferences dialog, even though the central preferences are overriding them.

Connections

You can configure the following settings for connecting to Perforce services:

When the application launches:

  • Show the Perforce Connection dialog: Always prompt for connection settings when launching P4V.

  • Restore all previously opened connections: Do not prompt for connection settings; reconnect to the Perforce service to which you were connected during your last session.

Opening and closing connections:

  • Use IP-specific tickets when logging in: Specifies whether your login ticket is restricted to the IP address from which you are connecting.

  • Automatically log off when closing a connection: Specifies whether your ticket is invalidated when you log out.

  • Don't expand Workspace and Depot trees to their previous state when opening connections: Specifies whether the trees are initially displayed expanded only at the top (depot) level.

Streams

To configure the way P4V handles workspaces when you perform stream operations, select one of the following:

  • Use the same workspace and switch it between streams: Enables you to continue using the same workspace when you switch between streams. Select this option if you regularly use streams with nearly identical workspace views and do not want to re-sync (retrieve) large amounts of redundant content each time you switch streams.

  • Use a different workspace for each stream: This is the default option and typical when a developer uses a main workspace, development workspaces, and release workspaces to manage his or her local work. If you select this option, you can still switch a workspace between streams by dragging the workspace icon from one stream to another in the Streams graph.

    • Don't warn me when switching workspaces: Specifies whether P4V switches workspaces silently when you switch streams.

  • Automatically update the workspace with all stream files when switching between streams: Syncs (retrieves) files to your workspace when you switch between streams without being prompted.

  • When branching streams, include file deletion actions (Server 12.1 or later): Select to include files that were deleted from the parent stream when Perforce populates the child stream. Equivalent to p4 populate -f command. The default behavior is to skip deleted files when branching to a new stream.

  • Don't allow streams to be reparented with drag and drop in the stream graph: Select to prevent accidental reparenting.

  • Stream graph: select the default name display and stream node width when viewing streams in the Stream Graph. To view the full depot path of the task stream in the Stream Graph, select Stream Root. Select Name to view the stream name only. You can override these defaults in Graph View Options on the Streams tab.

Server Data

You can configure how much data P4V processes during a session to minimize server load for frequently-run commands and large data transfers:

  • Check server for updates every n minutes: Specifies how often P4V checks the Perforce service for updated file information. Frequent checks enable P4V to display current file status but increase the workload on the Perforce service.

  • Maximum number of files displayed per changelist: Specifies the maximum number of files displayed in a changelist, to help minimize the time required to handle and submit very large changelists. This setting affects only the display of changelists, and does not limit the number of files that a changelist can contain. Any files beyond the maximum number are displayed as a plain text list.

  • Maximum size of file to preview (excludes audio and video files): Limits the size of image files displayed in the Preview tab on the Files pane, to limit the amount of image data sent from the Perforce service to P4V.

  • Number of changelists, jobs, branch mappings or labels to fetch at a time: Specifies the number of specifications read in each batch fetched, to minimize server load and maximize P4V performance. To retrieve all entries, specify 0.

Behavior

You can configure the following general P4V user interface behaviors.

Prompts:

  • Warn before reverting files: Specifies whether P4V displays a prompt before reverting files.

  • Warn when ignored files are not marked for add: Select to view a warning when you attempt to mark a file in your workspace for add and it is included in an ignore list.

    If you have created ignore lists and set the ignore list file name as the local P4IGNORE environment variable, P4V will not mark the files and file types listed in those ignore lists for add. The warning appears when you attempt to mark such a file for add or use the Reconcile process to add the file to the Perforce depot.

    For more information about ignore lists and P4IGNORE, see the P4 User's Guide.

  • Prompt for changelist when checking out, adding, or deleting files: Specifies whether P4V displays the "Choose changelist" dialog when you open files.

  • Prompt to get latest revision when checking out files that are out of date: Specifies whether P4V displays a prompt to get the latest revision when you attempt to check out files from an earlier revision.

  • Prompt when connecting to a new Perforce Sandbox: Specifies whether P4V displays a prompt before you connect to a new Perforce Sandbox.

Drag and drop:

  • Enable integration on directory-to-directory drag and drop: Launches the Merge/Integrate dialog when you drop a folder on another folder.

  • Enable diff comparisons on file-to-file drag and drop: Launches the Diff dialog when you drop a file on another file.

Merge-Integrate

You can configure default behaviors for the Merge-Integrate dialog.

  • Specify the default merge method that appears when the dialog opens:

    • Specify source and target files: the dialog prompts you to select source and target files

    • Branch mapping: the dialog prompts you to select a branch mapping

    • Remember my last choice: the dialog opens with the merge method you used the last time you opened the dialog

    You can set different default merge methods depending on whether you open the Merge/Integrate dialog from a file or folder (non-stream) or a submitted changelist.

    Note

    You cannot set the merge method that appears by default when you open the Merge/Integrate dialog from a stream object or branch mapping, since the merge method for a stream object is always Stream-to-stream and the merge method for a branch mapping is always Branch mapping.

  • Specify how to treat the files that you use to filter a branch mapping:

    • Source: the files that you include are treated as the source

    • Target: the files that you include are treated as the target

    • Remember my last choice: the dialog treats the files the way it did the last time you opened the dialog

  • Specify which Options tab appears on top when the Merge/Integrate dialog opens:

    • Resolve and Submit

    • Filter

    • Advanced

    • Remember my last choice

  • Specify the default Resolve and Submit options:

    • Add files to pending changelist or Automatically submit after resolving

    • Automatically resolve files after merging (select one of the resolve methods)

    • Pending changelist: default or new

    • Add previously linked job(s) to the new changelist

  • Specify whether to Check for opened files and warn prior to merging.

    This option checks to see if any of the files selected for merging are open for other actions.

Click Restore Defaults to change the settings back to Perforce's defaults.

For more information about these options, see Merging Files Between Codelines.

Integrate Flags

Integrate flags can be applied when the Merge/Integrate and Branch dialogs run the p4 integrate command. You can configure these integrate flags to be applied by default.

  • Do not copy newly branched target files to workspace (-v): Create a branch in the depot without retrieving the corresponding files from the depot to your workspace.

  • Enable baseless merges (-i): Perform the integration even if source and target share no common ancestor, using the most-recently-added revision of the source file as the base.

  • Try to integrate changes when source deleted and re-added (-Di): If the target file has been deleted and the source file has been changed, this option re-branches the source file on top of the target file. If the source file has been deleted and the target file has changed, this option deletes the target file. By default, outstanding edits cannot be integrated with a deleted file.

  • Force integration on all revisions, disregarding integration history (-f): Integrate all revisions of source and target files, including revisions that have already been integrated. Typically used with a specified revision range.

  • Do not get latest revision of selected files (-h): Use the workspace revision of the target file. By default, the head revision of the target file is automatically retrieved into the workspace before integrating.

  • Disregard indirect integration history (-1): Restrict selection of the base file revision to direct (parent-to-child or child-to-parent) integration history.

  • Propagate source filetypes to target files (-t): Assign the target file the same file type as the source file (when integrating to existing target files).

  • Schedule 'branch resolves' instead of branching new target files (-Rb): Schedules a branch resolve, instead of branching new target files automatically.

  • Schedule 'delete resolves' instead of deleting target files (-Rd): Schedules a delete resolve, instead of deleting target files automatically.

  • Skip previously merged 'cherry-picked' revisions to improve merge results (-Rs): Skips cherry-picked revisions that have already been integrated. This option can improve merge results, but can also require multiple resolves per file.

These integrate flags are applied with different Perforce commands, depending on the dialog, integration method, and Perforce Server (P4D) version:

g Condition Command Available Flags

Merge/Integrate

Stream-to stream method

p4 merge

None

Merge/Integrate

Branch mapping and Files and Folders methods

p4 integrate

All

Copy

Command available only with Perforce Server 2011.1 and up

p4 copy -v

Branch

Perforce Server 2010.2 and earlier

p4 integrate -v

Branch

Perforce Server 2011.1 and up

p4 populate

None

For more information about these Perforce commands, see the Perforce Command Reference.

Copy

You can configure default behaviors for the Copy dialog.

  • Specify the default copy method that appears when the dialog opens:

    • Specify source and target files: the dialog prompts you to select source and target files

    • Branch mapping: the dialog prompts you to select a branch mapping

    • Remember my last choice: the dialog opens with the copy method you used the last time you opened the dialog

    You can set different default copy methods depending on whether you open the Copy dialog from a non-stream file or folder or a submitted changelist.

    Note

    You cannot set the copy method that appears by default when you open the Copy dialog from a stream object or branch mapping, since the copy method for a stream object is always Stream-to-stream and the copy method for a branch mapping is always Branch mapping.

  • Specify how to treat the files that you use to filter a branch mapping:

    • Source: the files that you include are treated as the source

    • Target: the files that you include are treated as the target

    • Remember my last choice: the dialog treats the files the way it did the last time you opened the dialog

  • Specify which Options tab appears on top when the Copy dialog opens:

    • Submit

    • Filter

    • Advanced

    • Remember my last choice

  • Specify the default Submit options:

    • Add files to pending changelist or Automatically submit copied files

    • Pending changelist: default or new

    • Add previously linked job(s) to the new changelist

  • Specify the default Advanced option:

    • Do not copy newly branched target files to workspace (-v): Create a branch in the depot without retrieving the corresponding files from the depot to your workspace.

Click Restore Defaults to change the settings back to Perforce's defaults.

For more information about these options, see Merging Files Between Codelines.

Branch

You can configure default behaviors for the Branch dialog.

  • Specify the default branch method that appears when the dialog opens:

    • Specify source and target files: the dialog prompts you to select source and target files

    • Branch mapping: the dialog prompts you to select a branch mapping

    • Remember my last choice: the dialog opens with the branch method you used the last time you opened the dialog

    You can set different default branch methods depending on whether you open the Branch dialog from a non-stream file or folder or a submitted changelist.

    Note

    You cannot set the branch method that appears by default when you open the Branch dialog from a stream object or branch mapping, since the branch method for a stream object is always Specify source and target files and the branch method for a branch mapping is always Branch mapping.

  • Specify how to treat the files that you use to filter a branch mapping:

    • Source: the files that you include are treated as the source

    • Target: the files that you include are treated as the target

    • Remember my last choice: the dialog treats the files the way it did the last time you opened the dialog

  • Specify which Options tab appears on top when the Branch dialog opens:

    • Submit

    • Filter

    • Advanced

    • Remember my last choice

  • Specify the default Submit options:

    • Add files to pending changelist or Automatically submit branched files

    • Pending changelist: default or new

  • Specify the default Advanced option:

    • Do not copy newly branched target files to workspace (-v): Create a branch in the depot without retrieving the corresponding files from the depot to your workspace.

Click Restore Defaults to change the settings back to Perforce's defaults.

For more information about these options, see Creating Branches.

Double-click

You can select what you want to happen when you double-click various object types in P4V. Select a double-click behavior for an object by clicking in the Double Click Behavior column to open a drop-down list. The behaviors available for selection in the drop-down list depend on the object.

Click Restore Defaults to return all objects to their default setting, which is always the first selection in each drop-down list.

Shortcuts

You can enter keyboard shortcuts for commands used in the main P4V window, Revision Graph viewer, Folder Diff utility, and Time Lapse View.

To enter or edit a shortcut:

  1. In the Shortcuts for drop-down, select the shortcut type:

    • P4V

    • Revision Graph

    • Folder Diff

    • Time-Lapse View

    Only shortcuts for the selected window, viewer, or utility show in the shortcut list.

  2. Click the Shortcut column for the command.

    You may need to scroll the list window to the right to view the Shortcut column.

  3. Enter the keyboard shortcut in the edit field.

    Shortcuts must include either the command key, control key, or a function key

  4. Click OK.

Some commands come with default keyboard shortcuts. You can restore all defaults by clicking Restore Defaults, or set an individual command to use a default by selecting the command row and clicking Use Default.

Logging

You can configure the following logging options:

Log pane options:

  • Show p4 reporting commands: Specifies whether the log pane in the P4V window displays all commands issued by P4V, including commands issued by P4V to obtain status information from the Perforce service.

  • Show p4 command output for file operations: For verbose log messages, enable this option.

Logging to a file:

  • Enable logging to file: Logs P4V activity to the specified file.

    • Name: Specifies the name and location of the log file.

    • Size: Specifies the maximum size of the log file in kilobytes (KB).

Display

You can configure the following P4V display and localization options:

Application:

  • Show item count on tab bar of details pane: For the Submitted tab, toggles display of the number of files and job fixes in the tab bar of the details pane (below the Submitted list).

  • Show the What's New in P4V page after upgrading: Display the What's New page as a tab in the P4V window.

  • Dates: Sets the date format used throughout P4V:

    • OS format: Use the format that your operating system uses.

    • Perforce standard (yyyy/mm/dd hh:mm:ss)

  • Show date and time as:Specify whether to show the date and time for the shared versioning service (Server time) or for your local client.

Localization:

  • Language used for application menus, labels, and dialogs (requires restart): Select English or, if it is available, Japanese.

  • Set encoding for all connections to: Sets the character encoding for connections to unicode-mode Perforce services.

    If you do not set the encoding here, you are prompted to enter the character encoding every time you set up a connection to a unicode-mode Perforce service. The encoding that you set here does not affect service connections whose character encoding has already been set at connection. If you are unsure which setting to choose, consult your Perforce administrator.

  • Use the system character encoding in P4Merge when connected to non-unicode servers: When enabled, overrides P4Merge's logic for determining character encoding (to preserve pre-2010.1 behavior).

Files and History

You can configure the way P4V displays files and file icons:

  • Use a distinct file icon for modified files: Specifies whether P4V indicates files that you have edited after syncing them to your workspace.

  • Show Perforce filetype for files in the Workspace and Depot tree: Toggles display of filetype in the tree panes.

  • Show revision information for files in the Workspace and Depot tree: Toggles display of revision numbers in the tree panes.

  • Render thumbnails for Maya files: Enables P4V to display thumbnail images of Maya media files.

  • File preview font: Specifies the font that P4V uses to display files in the preview pane.

    Click Show fixed sized fonts only to limit the selection in the font drop-down to fixed-sized fonts.

  • Hide files/revisions from 'task' streams (when following branch, copy actions): Filters out file revisions that were submitted to task streams when you view file history

Features

You can enable or disable the following features. When you disable a feature, the tabs and dialogs associated with the feature no longer display in P4V.

Features:

  • Labels

  • Jobs

  • Streams

  • Unload/Reload

Menu options:

  • Merge, Copy and Branch Dialogs

  • Set up Connection Assistant / Connection Wizard

  • Sandbox Configuration

  • Revision Graph

  • Custom Tools

  • Time-lapse

  • Administration Tool

All of the above are enabled by default. You must restart P4V for changes to take effect. For information about these features, see the appropriate section of this user guide.

Tools

You can configure the following Revision Graph and Time-Lapse View options:

Revision Graph:

  • Use software rendering for Revision Graph: Enable only if your machine is having problems rendering Revision Graph output. For details, consult the Perforce Knowledge base.

  • Limit Revision Graph to ancestors and descendants: Controls how much of a file's integration history is displayed.

Time-Lapse View:

  • By default Time-lapse view should show: Specifies whether Time-lapse View displays only direct file history, branch (integration/merge) history, or information about the originating changelist for the selected file by default.

    You can also select these display preferences in Time-lapse View. For more information about these options, see Viewing Image File History with Time-lapse View. For more Image Time-lapse preferences, see Image Timelapse.

Image Timelapse

Default revisions to retrieve for Image Time-lapse View: Specifies whether you want P4V to prompt you for the number of revisions to view when you use Time-lapse View, whether to limit the retrieved revisions to a certain number, or whether to view all revisions. You can improve performance by limiting the number of large image files retrieved at a time.

Image Time-lapse View Filetype Associations: Specifies whether you want to open files as images in Time-lapse view, and which image types to view as images. You can improve performance by limiting image rendering in Time-lapse view.

File Editors

To associate file types with the applications you use to edit them:

  1. Click Add.

  2. Select a file extension from the drop-down list.

  3. Enter or browse for the associated application.

  4. (Optional) Select Always use the selected application to open files of this type to set the application as the default.

  5. Click Save.

You can enter as many applications as you like for each extension. All of the applications will appear as options when you context-click a file in P4V and select Open With.

Note

Any application that you've used to open a file from the context menu in P4V appears by default as an associated application on the File Editors page in the Preferences dialog, unless you remove it.

Diff

To set the default diff application, select one of the following:

  1. P4Merge: Perforce's companion diff tool.

  2. Other application: Browse to your preferred diff tool.

    To specify arguments for third-party diff applications, enter %1 for the name of the first file and %2 for the name of the second file in the Arguments field. Perforce replaces these placeholders with the actual filenames when calling the diff application.

To assign diff applications by file type:

  1. Click Add.

  2. Select a file extension from the drop-down list.

  3. Enter or browse for the associated application.

  4. Specify arguments for third-party diff applications in the Arguments field:

    Enter %1 for the name of the first file and %2 for the name of the second file. P4V replaces these placeholders with the actual filenames when calling the diff application.

  5. Click Save.

    The extension and associated application are displayed in the list of file type-application associations.

Merge

To set the default merge application, select one of the following:

  1. P4Merge: Perforce's companion merge tool.

  2. Other application: Browse to your preferred merge tool.

    To specify arguments for third-party merge applications, enter the following replaceable parameters in the Arguments field:

    • Base file: %b

    • Their/Source file: %1

    • Your/Target file: %2

    • Result file: %r

    Perforce replaces these placeholders with the actual filenames when calling the merge application.

To assign merge applications by file type:

  1. Click Add.

  2. Select a file extension from the drop-down list.

  3. Enter or browse for the associated application.

  4. Specify arguments for third-party merge applications in the Arguments field:

    Enter the following replaceable parameters in the Arguments field:

    • Base file: %b

    • Their/Source file: %1

    • Your/Target file: %2

    • Result file: %r

    Perforce replaces these placeholders with the actual filenames when calling the merge application.

  5. Click Save.

    The extension and associated application are displayed in the list of file type-application associations.

Applets

Your administrator can enable Perforce services to serve applets that can run in P4V. In order for these applets to run in P4V, you must enable applets in your P4V preferences. For more information about Perforce applets, see the Perforce JavaScript API for Visual Tools Users Guide or consult your Perforce administrator.

To enable Perforce applets to run in P4V:

  1. Select Allow Perforce applets to run in P4V.

  2. Specify the Perforce services from which you are willing to accept Perforce applets:

    • Enter the Perforce service name or host:port in the Server field.

    • Click Add.

  3. Click Advanced...to specify the following settings:

    • Save cookies from applets (Click Remove Cookies to delete all applet-generated cookies)

    • Allow applets to store data locally

    • Manually configure web proxy used by applets for internet access: Enter the web proxy address and port.