With 'Allwrite' off, have an option to skip syncing from Perforce when read-only is unchecked

[julien329]

With 'Allwrite' off, have an option to skip syncing from Perforce when read-only is unchecked. This skips unnecessary perforce delays when resuming editing after saving and would also allow to work with already checked-out files while perforce is down.

[botman99]

I'm not sure I understand the request. P4SimpleScc doesn't sync anything from Perforce. If you want to work on files while Perforce is down, you can temporarily disable P4SimpleScc for the current solution.

[julien329]

Because we have a slow connection to a perforce server overseas, all perforce operations tend to hang for a while. This makes visual studio wait every time we send a perforce request through P4SimpleCC.

This means that using "Check out files on modify" hangs the editor every time we modify a file after saving. A useful improvement for us would be an option for P4SimpleScc to first check the file’s state on modify, and only issue a Perforce checkout request if the file is actually in a read-only state.

[botman99]

I created this issue to perform Perforce commands in a background thread to prevent a slow (or dead) Perforce server from locking up Visual Studio...

#9

That should solve the issue of locking up Visual Studio while waiting for a file to be checked out.

I can also look at adding an additional option to not check with the Perforce server if files are not read-only (and just assume they are checked out).

[julien329]

Interesting, I like the idea of a background thread too, I'm guessing it would solve the issue as well. You can close this one as duplicate then!

[botman99]

I actually think it is still useful to have something like the 'allwrite' option, but that option depends on the workspace being set up with the 'allwrite' setting in P4V. Having some additional setting that say "skip Perforce checks on files that aren't read-only" would also be useful (for some people).