[p4] P4V and check out of a binary file not at latest revision

[Francis Paulin]

Hi and sorry for the spam, I just think of another way we use here to
prevent the problem

Using p4 typemap command, add every binary file in the depot with the +l
flag. 
For example:
binary+l  //....dds
binary+l  //....bmp

In that example, doing this will disallow multiple opens for .dds and
.bmp files. 
Since only one user at a time can check-out the file, no resolve will
ever be required. Perforce will prevent other users from doing an "open
for edit" on the file. Actually, I recommend doing this on every binary
assets you have in the depot since no merge is possible for those files
:o).

Be aware that modifying the typemap table will not affect files already
in the depot but only the new ones added!
For files already in the depot, do as follows:
   * Open for edit all files you want to add the +l flags.
   * Select the file, right click on it and choose "Change File type..."
   * Make sure the +l Checkbox is checked!

Note that you can do a "change file type" with multiple files selected.
With P4Win, only one pop-up will appear changing every file at once (so
make sure that they already have the same type). P4V will pop-up a file
type window for each file selected.

Hope this help (and sorry for the spam again) :o)
Francis

-----Original Message-----
From: Francis Paulin 
Sent: April 12, 2007 7:58 PM
To: 'Melissa'; 'Nancy Nadeau'; perforce-user at perforce.com
Subject: RE: [p4] P4V and check out of a binary file not at latest
revision

Hi,

Yes you can do that, but with a nasty surprise :o).

If the user accepts "yours" he/she will loose changes from revision #8,
#9 and #10 overwriting them with revision #7 + his/her changes done to
the file.

If the user accepts "theirs" he/she will lose all modifications done on
the binary file. Therefore, if submitted, the revision #11 will be an
exact copy of revision #10. Oops :o).

In that case the only thing the user can do is revert the file, get the
latest, open for edit and redo the change over again. This is unwanted
and a big waste of time especially if we think about a lot of
modifications done on a textures or worst: a 3D model.

I think the P4Win functionality of asking to "Sync then Edit" as been
requested for P4V several times in the past. The latest version of P4V
does not offer it yet. Hopefully, Perforce people will take time to
provide it in a near feature!

Hope this help!
Francis



-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Melissa
Sent: April 12, 2007 7:09 PM
To: 'Nancy Nadeau'; perforce-user at perforce.com
Subject: Re: [p4] P4V and check out of a binary file not at latest
revision

You can and must resolve the binary file. Merging is not a choice for a
binary file though. Your user should choose accept yours (The version
from
his client) or accept theirs (the head revision from the server) when
resolving.


-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Nancy Nadeau
Sent: Thursday, April 12, 2007 12:56 PM
To: perforce-user at perforce.com
Subject: [p4] P4V and check out of a binary file not at latest revision


Here we go for my first posting (well... not one sent by an out of
office 
agent ;-))

I have the following scenario:
* a file mytexture.bmp (a binary file) is at version 10 on the server
* an artist is synced with version 7.
* he does a Check Out in P4V
* a little message in the log window gets displayed saying that he will
have

to resolve #8,#10 before submitting.

But since it's a binary file that will never be possible!!!

In P4Win there is a dialog that pops up and it gives you the possibility
to
do 
Sync then Edit... but I can't find an option that would give me the
equivalent 
in P4V. Am I missing something?

Or is the only solution to write a script to make sure an artist checks
out 
the latest revision?

Of course one could say that the artist could have noticed before doing
the 
Check Out that he was not synced to the latest revision since it's
written
at 
the end of the file 
    mytexture.bmp #7/10 <binary>
But for those of you who deal with artists you surely know that it's not
the

kind of things that most of them notices... ;-)
So how do you deal with this?

Thanks,

    Nancy

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user