This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Auto refresh of file status in CPC v16

I am now working on the CPC v16 and I've never noticed this before, so I am wondering if this is new.

In the content perspective, I'm looking at files grouped by status.

With All descendants checked, I have thousands of files that are current and a few that are Out of Date. If I select a single Out of Date file and check it out, it used to only switch to current. Now, it switches to current, and gets inserted in the current group, and the group gets expanded to show the file.

To go back to my previous list display, I have to scroll back up the Current group to collapse it.

Is there a way to turn off this behavior (that is, only update the status until I choose to refresh my pane.)

Thanks,

Parents
  • 0

    Any resolution on this?  Turning off the watcher doesn't resolve this on 17.2 either.  We recently upgraded straight to 17.2 from pre 16 and developers who are selectively checking stuff out don't like it refreshing every time they check a file.  This "feature" really interrupts work flow.

  • 0 in reply to 

    Try turning off Automatic refresh under Personal Options/MPX ( keeping MPX on) .  It is a trade-off, now you will have to press F5 for the display to refresh. Let's say another developer checked in a file while you were using CPC, you would not see the change until you press F5.  Personally I use it this way. 

Reply
  • 0 in reply to 

    Try turning off Automatic refresh under Personal Options/MPX ( keeping MPX on) .  It is a trade-off, now you will have to press F5 for the display to refresh. Let's say another developer checked in a file while you were using CPC, you would not see the change until you press F5.  Personally I use it this way. 

Children
  • 0 in reply to 

    It did not wok keeping MPX on, but that may be happening because the server is not configured for MPX and I don't have it specified under server properties either.  Seems like a lot of reconfiguring in the hopes that might prevent StarTeam from jumping from my out of date grouping to the current grouping when I check out a single file.  When I have time, I may try setting up MPX, but not sure that really buys that much for us, that is why I never set it up before.  It looks like MPX uses different ports so I have to open additional firewalls, which means changes to security diagrams so security will authorize that.  Hopefully, I can run MPX on the same server running StarTeam server so I don't have to request another virtual server.  

    I'm leaning toward telling developers to install the StarTeam 15 client instead of 17.2 if they do not like the behavior.