Author Topic: beta2: Version Control (perforce) - phantom directories.  (Read 2823 times)

jporkkahtc

  • Senior Community Member
  • Posts: 2433
  • Hero Points: 202
  • Text
beta2: Version Control (perforce) - phantom directories.
« on: May 04, 2013, 07:18:28 pm »
Compare project to perforce:
   Open "Perforce Update Directory" window.
   I'm working with an Android project.
   The top several entries in the dialog are:
   E:\
   E:\src\
   E:\src\p1deohub\
   E:\src\p1deohub\ui
   E:\src\p1deohub\Settings
   FooDialog.java
   E:\src\p1\blah\trunk
   E:\src\p1\blah\trunk\ui
   E:\src\p1\blah\trunk\ui\bin\
   E:\src\p1\blah\trunk\ui\bin\classes
   E:\src\p1\blah\trunk\ui\gen\
   E:\src\p1\blah\trunk\ui\src\
    ....
   blah.vpj
   blah.vpw
   blah.vpwhist
   blah.vtg
   
Now, "p1deohub" is not a directory on disk nor is it in anyway part of the project
This is totally made up by Slickedit.
The path on disk is E:\src\p1\blah\trunk\.....
"videohub" appears in the AndroidManifest.xml file as part of the package name, but it is not a top-level directory name anywhere.

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2680
  • Hero Points: 143
Re: beta2: Version Control (perforce) - phantom directories.
« Reply #1 on: May 06, 2013, 02:04:09 pm »
Are these from different Perforce clients?

jporkkahtc

  • Senior Community Member
  • Posts: 2433
  • Hero Points: 202
  • Text
Re: beta2: Version Control (perforce) - phantom directories.
« Reply #2 on: May 06, 2013, 03:17:10 pm »
No, well, I don't think so.
I didn't see how to configure a client in Slickedit.
I have E:\src\p1\.... and E:\src\p2\... and E:\src\p3\...
as three different clients, but this problem doesn't seem related to that.

Does slick write a log of the P4 commands it runs someplace?
It ought to if it doesn't.

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2680
  • Hero Points: 143
Re: beta2: Version Control (perforce) - phantom directories.
« Reply #3 on: May 06, 2013, 03:23:06 pm »
If you set def_svc_logging to 1, you will get output in (config)/(version)/logs/svc.log.  It generates quite a bit of output.

jporkkahtc

  • Senior Community Member
  • Posts: 2433
  • Hero Points: 202
  • Text
Re: beta2: Version Control (perforce) - phantom directories.
« Reply #4 on: May 06, 2013, 08:59:58 pm »
Code: [Select]
HM...so today VS isn't showing bogus paths, but it is still behaving oddly.
I have three Android projects in my workspace (call them A, B, C).
The perforce enlistment root is E:\src\p1
They live at:
    E:\src\p1\blat\trunk\A
    E:\src\p1\blat\trunk\B
    E:\src\p1\blat\trunk\C
When I compare workspace with Perforce the "Perforce Update Directory" window is populated with:
First,  a tree rooted at "E:\" but limited to the contents of E:\src\p1\blat\trunk\B and E:\src\p1\blat\trunk\C. (So, the entire "E" drive is not included).
Second, a tree rooted at "E:\src\p1\blat\trunk\A"

So it looks like: (Where "+" is the little triangular doodad in tree views)
    +E:\
        +E:\src\p
            +E:\src\
                +E:\src\p1\
                    +E:\src\p1\blat\
                        +E:\src\p1\blat\trunk\
                            +E:\src\p1\blat\trunk\B\
                                +E:\src\p1\blat\trunk\B\bin\
                                +E:\src\p1\blat\trunk\B\gen\
                                +E:\src\p1\blat\trunk\B\src\
                            +E:\src\p1\blat\trunk\C\
                                +E:\src\p1\blat\trunk\C\bin\
                                +E:\src\p1\blat\trunk\C\gen\

    +E:\src\p1\blat\trunk\A\
        +E:\src\p1\blat\trunk\A\bin\
        +E:\src\p1\blat\trunk\A\gen\
        +E:\src\p1\blat\trunk\A\src\
            +E:\src\p1\blat\trunk\A\src\com\
                    +E:\src\p1\blat\trunk\A\src\com\ ......

         ?A.vpj
         ?A.vpw
         ?A.vpwhist





Notably, E:\src\p1\blat\trunk\C\src\ is not in the treeview at all.
I don't see anything amiss in the svc.log file.


Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2680
  • Hero Points: 143
Re: beta2: Version Control (perforce) - phantom directories.
« Reply #5 on: May 07, 2013, 12:13:02 pm »
Were there any files modified/out-of-date in the C folder?