About P4V icons
P4V uses a variety of icons and badges (decorations) to depict Perforce objects and their status. The following table describes commonly-encountered icons.
P4V displays file icons in the the Tree pane and throughout the user interface, with file status indicated as shown in the following table. Note that file icons might be displayed with multiple "badges" (for example, check marks, lock indicators), each indicating an aspect of the file's status. This table does not list all the possible combinations. Note that red badges indicate actions taken by you, and blue badges indicate actions taken by another user. To display a tooltip containing more details about a file's status, hover the mouse pointer over the file.
|
File in depot |
|
|
File in depot but not mapped by workspace view |
|
|
File in workspace differs from head revision |
|
|
File in workspace but not in depot |
|
|
File synced to head revision |
|
|
File synced to previous revision |
|
|
File needs to be resolved |
|
|
File locked by you |
|
|
File locked by other user |
|
|
File open for add by you (red "+") |
|
|
File open for add in other workspace (blue "+") |
|
|
File open for edit by you (red check mark) |
|
|
File open for edit by other user (blue check mark) |
|
|
File open for delete by you (red "x") |
|
|
File deleted in depot |
|
|
File open for delete by other user (blue "x") |
|
|
File open for move/rename ("x" indicates source, "+" indicates target) |
|
|
File open for branch |
|
|
File open for integrate (will need resolve) |
|
|
Shelved file in pending changelist |
|
|
Symbolic link |
|
|
File imported from another stream (cannot be submitted to current stream) |
|
|
Pending changelist has files that need resolve |
|
|
Pending changelist contains shelved files |
|
|
(Blue folder) A folder in the Perforce depot |
|
|
(Yellow folder) A folder in your client workspace |
|
|
(White folder) A folder that resides on your local machine outside your client workspace root |
|
|
Spec depot: when enabled by your Perforce administrator, a spec depot stores the history of changes to Perforce specifications such as changelists. |
|
|
Remote depot: if configured by your Perforce administrator, a remote depot maps a portion of another Perforce repository as if it were a depot. Typically used to enable you to import and export third-party files without providing outsiders with access to your Perforce service. |
|
|
Stream depot: A depot where stream files are stored. |
