0

I'm using P4 client

(Perforce Visual Client/NTX64/2014.3/1007540, OS: Win8.1),

and wand the "Allwrite" option in my workspace to be always on (enables me to edit files without checking them out before).

After I check that option in my workspace

(Connection->Edit Current Workspace...->Advanced->File Options->[checkbox]Allwrite ),

it works as expected, and my files stay writeable.

Problem is, after I close P4V, the "Allwrite" flag returns to it's default value (which is: unchecked).

Any idea how to do that? (Maybe passing it as a parameter on P4V launch, P4 console or whatever?)

I searched the web (this is the only question on the subject I've found, but it doesn't cover mine: p4sandbox-files-are-readonly-even-with-setting-allwrite), and didn't find any solutions...

set the allwrite option

P.S.

Please spare the: "you shouldn't use P4 that way", and the: "you're probably a git user. in P4 we do things differently". For the ones of you that can't stop of asking me that, lets say my question is only a theoretically one.

Community
  • 1
  • 1
Captain Crunch
  • 567
  • 3
  • 13
  • Hi Cap'n. I'm using the same version as you. I don't see this behavior. What happens if you display the workspace via the command line ('p4 client')? – tkosinski Aug 11 '15 at 18:33
  • @tkosinski: din't know about the 'p4 client' command. thnx!. but still, it doesn't work. iv'e edited the client spec file (the file that `p4 client My_Worksspace_Name` command has opened), and changed the flag i want (noallwrite -> allwrite), but when i save and close the file i'm getting this output: `Client My_Worksspace_Name not changed.` (and of course the spec file didn't change. do you have any idea what i'm doing wrong? – Captain Crunch Aug 12 '15 at 09:52
  • That's sure a head-scratcher. Do you have the spec depot enabled? If so, you should be able to view the client and any history (and any changes to it). Or view the client from another workstation? I would guess this would be an interesting question for Perforce Support. – tkosinski Aug 12 '15 at 14:04
  • @tkosinski: i'll try your advice about the spec depot – Captain Crunch Aug 13 '15 at 06:04
  • Have you talked with your Perforce administrator? This could be due to a trigger that the administrator has installed on your server. – Bryan Pendleton Aug 16 '15 at 16:08
  • @BryanPendleton: might. i'll check – Captain Crunch Aug 17 '15 at 06:38

0 Answers0