[p4] Mapping of development setup files
Arieh Schneier
ASchneier at bluetongue.com
Sun Oct 14 18:08:01 PDT 2007
(Sorry for the slow reply, I have been on holiday, then took a few days
to get a chance to go back through the mailing list)
>> I tried this with null and at first it appeared to be working but I
couldn't see the second mapping.
> P4v just displays nothing in Workspace view.
> I think this is a bug and should be fixed, but that doesn't help you
for now.
This is a bug in P4V which we have reported to P4 months ago (in
January) but are still waiting for the fix. I did discover a workaround
that we use in the meantime (which it seems you may have stumbled across
above but didn't realise why).
If you open the Depot view, then select a file that is mapped to the
drive (I haven't tried with folders, I have been mapping the entire
drives, so just replace drive with folder if that suits you better) you
want in the 'Files in Folder' window, then select the Workspace view,
the drive that that file was under will appear. If you then go back to
the Depot view, select a file that is under the second mapping and then
switch back to the workspace view, that next drive will then appear.
In short, we use the mapping to NULL and mostly use the Depot view. Any
time we want to add a file (or view them) using the Workspace view, you
need to select a file in the 'Files in Folder' window (using the Depot
view) then select the Workspace view.
Very annoying bug, that needs to be fixed....
Arieh.
More information about the perforce-user
mailing list