Check-in update issue

Thomas Linder Puls · Post by **Thomas Linder Puls** » Mon Jan 21, 2008 7:21 am

We check-out files from our development environment (using a command script).

But we commit our changes from the Vault GUI client.

Therefore the GUI client is (fair enough) not always up-to-date on the check-out state when we switch to it.

When we press Commit All we get the following problem:

The check-out list does not contain all files that should be committed
But it is not easy to spot this problem.
When the commit is complete the GUI client refreshes the state, revealing the files that was not committed (by Commit All)

If we remember to press F5 before we commit there is no problem. F5 does not seem to be a very expensive operation, and it seems to be that operation that is made after the transaction completes.

We would be very pleased if "Commit All" first did a refresh (F5) and then the actual Commit All, such that Commit All actually committed all changes.

Beth · Post by **Beth** » Mon Jan 21, 2008 5:32 pm

I can most certainly take a feature request. All feedback is appreciated.
Thanks. It sounds like the refresh would have to happen before the Commit All actually starts the committing.

Also, in the Vault GUI under Tools - Options, on the General page, you can set an auto refresh as well.

Thomas Linder Puls · Post by **Thomas Linder Puls** » Tue Jan 22, 2008 3:43 am

Thank you.

Perhaps "get focus" could also trigger a refresh.