Beta 3 - "Perforce : Show status on file icons" does not work

[sndom]

With Beta 3 64 bit on Windows 7, enabling the "Show status on file icons" setting for Perforce does not do anything.

No icon changes are visible (in the projects view) and the setting has reverted to off next time I look in the settings.

[Dan]

It worked in prior versions?  What happens if you restart the editor?

I don't think there were any changes to the feature itself between beta 2 and beta 3.

[sndom]

It worked in prior versions?

I don't think so.  At least I remember enabling it but don't remember noticing icons changing.

What happens if you restart the editor?

The setting has disabled itself when I restart it.

Dom

[Dan]

The only thing I see that resets it is the function that the dialog box would call to shut it off.  You can check the value, the variable is def_perforce_show_file_status.

Do you have a mix of projects where some do not use Perforce?

[evanratt]

I don't see the setting turning itself off, but I also only see the icons changing if I check a file out, to show that I have it out. There aren't any icons to indicate someone else has a file out.

Running the 32-bit version with the SCC DLL does show icons indicating the status.

[Dan]

We currently only support modified, out-of-date, and locally checked out.  Checked out by other is possible, but I tried to have the position dictate the status as much as the picture, and I'm almost out of positions.

[evanratt]

In that case, I guess it's working as designed for me. I would like to put a vote in for a "checked-out by other" status icon, if it's doable.

[sndom]

The only thing I see that resets it is the function that the dialog box would call to shut it off.  You can check the value, the variable is def_perforce_show_file_status.

If I switch the feature on either through the options dialog or by setting the macro directly it will stay switched on briefly, but when I check it a little later (with no intervening restart) it will have been disabled again.

I have seen it stay enabled, but not for long.

I have never seen any change to the icons in the project file tree.
There is no change when I check out a file.
If I check out a file and then quit and restart the editor there is no change.
If I try re-enabling the feature with files checked out I still get nothing.

Do you have a mix of projects where some do not use Perforce?

Yes.
There are 65 projects in the solution, most but not all with versioned files.  Some with just a few files that are not versioned.  Some projects share version controlled files with other projects.

Dom

[Dan]

I wonder if activating projects that don't have version control setup is shutting it off (although I've been switching frequently and have had no issue).

When you turn it on, you should be able to see p4.exe run in the background to get the statuses.

[sndom]

When you turn it on, you should be able to see p4.exe run in the background to get the statuses.

What command is it going to run?

[Dan]

It runs three different ones to gather all the information it needs.

• p4 -ztag opened
• p4 diff -sa
• p4 sync -n

[sndom]

Hi Dan

I can see one show stopping issue there:

p4 sync -n

We have a very large perforce depot here containing a large number of projects.  Rather than have a complex workspace mapping bits of this depot to my local machine, I map the entire depot then selectively check out just the parts I need.

With this setup, p4 sync -n is going to list almost every other file in the depot each time it runs.  This takes several minutes and generates a gigantic amount of output.

For this to be viable it is going to need to restrict the p4 sync to the folders containing the project files.

I took a quick look with procmon and saw these commands being run, but I presume it timed out on the p4 sync -n.  Would it disable the feature if it timed out?

Dom

[shadm]

I also have a fairly large depot that I work from.  If I leave this option turned on, not only does it take forever, but it will eventually eat up huge amounts of memory (even all of it) on the server, and it has also crashed my Perforce server twice that I know of.  I changed my workspace viewspec to correspond to a very small part of the depot, as that is the only part of the depot I need at the moment.  I would agree though, that if there is a way to limit the update to just the files/folders included in the project as sndom said, that would be better.

[Dan]

That is probably why it is not completing.

In both of your cases, would "p4 sync -n <workspacepath>" be correct?

[sndom]

In both of your cases, would "p4 sync -n <workspacepath>" be correct?

That would work for me

Dom