Skip to content

Instantly share code, notes, and snippets.

@rygorous
Created June 1, 2012 17:42
Embed
What would you like to do?
P4V wishlist
(All issues here reported for P4V NTX64/2012.1/459107 on Windows 7)
P4V UI/Workflow issues
======================
- Feature request: Auto-"Refresh all" when switching current task to P4V (WM_ACTIVATEAPP).
Reason: I frequently Alt-Tab to P4V to add a newly created file, only to not find it the
first time, then hit F5, then actually get to add it. "Refresh all" seems to be
reasonably fast, so why not automatically do it when the Window has to repaint anyway?
- Feature request: "Edit Current Workspace" dialog (or maybe "Environment Variables"?)
should have a "Save as p4config.txt" button, or just always do so automatically;
[and it would be nice if P4 automatically had P4CONFIG set to p4config.txt or another
standardized file name]
Reason: This makes for smoother inter-op with the command line tools (i.e. a Workspace
that is set up in P4V automatically works in all GUI and CL tools). This is probably
the least surprising alternative for users. Just as importantly, P4CONFIG seems to be
the only way (that I can tell) to make the Perforce Shell Extension (Explorer
Integration) work with multiple connections.
[Note that I regularly have to use multiple connections, which is probably atypical.]
- Bug: There seem to be several bugs wrt Window placement, all following the same general
pattern of maximized windows misbehaving. I'm using a multi-monitor setup and
frequently have P4V running maximized on one screen. With older versions of P4V,
just picking another connection from the favorites list would launch another
"maximized" P4V, but in the wrong position. The net result is that the Window bottom
right part of the Window is clipped off. Fixing this requires un-maximizing the window
then re-maximizing it, which is annoying. Somewhere between 2010.1 and 2012.1 this got
fixed, but even in 2012.1, there's still a variant of this problem: Run P4V maximized
on a secondary monitor, and make sure the "Branch mapping" tab is closed (any of the
tabs accessible from the "View" menu works to repro this). Then hit Ctrl-3 to open it.
At least on my machine this causes the P4V window to move, despite still having
"maximized" state as far as Windows is concerned.
- Defaults: Why is "Sort by/Resolve status" not the default? Particularly when dealing
with large CLs (e.g. during integrations), this is important.
- Feature request: "Sort by/Resolve status" - this should be a boolean flag (checkbox),
not have "radio button" semantics. I want to be able to sort on resolve status as a
"primary key" and still select what the secondary key is.
- Feature request: Use monospaced font for changelist descriptions, at least in the
"Submit"/"Edit" dialogs and the Changelist "description pane" (not sure what the
official name is). I realize this is a matter of taste but I'd like it to be an
option at least.
- Feature request: Only print first line of Changelist description in "History",
"Submitted" etc. views. Again a matter of taste, but just ignoring newlines
altogether and smushing everything into one line is hard to read. Another thing
where I'd just like the option.
- Bug: "Reconcile Offline Work" dialog - while the list boxes support multi-select,
clicking on one of the check boxes while having multiple files selected will only
select that item and clear the selection. Ctrl-Click won't clear the selection, but
will still only toggle the check box on that one item.
- Feature request: "Reconcile Offline Work" can deal with one directory and its children
recursively, but is disabled when two directories are selected. Is it possible to lift
this restriction?
====
- Feature request: In history view, I can right-click on a revision and select "Get Revision...",
but then I need to manually add the list of folders to get. In the workspace view, I can right-
click on a folder and select "Get Revision...", but then I manually need to enter the Revision/
Changelist number or a date.
@rdefauw
Copy link

rdefauw commented Jun 1, 2012

I'm going to pass this along to our support crew...

@rdefauw
Copy link

rdefauw commented Jun 1, 2012

Hi,

If you don't mind, you can send this list directly to support@perforce.com. Since it's a comprehensive list, it's easier for them to work with you directly and let you know about any workarounds. Let me know if that's not feasible...

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment