VB6: "Source Code Control Results" window remains

lzandman · Post by **lzandman** » Tue Jan 18, 2005 4:51 am

Hi,

Today I had to work on some old Visual Basic 6 code and I noticed the Vault (V3.0.0 2752) client integrated nicely with the VS6 IDE (normally I use VS2003 without Vault integration; I prefer using the Vault client itself).

However I noticed that when checking in some files sometimes the "Source Control Results" window, which shows Vault's status messages, doesn't automatically disappear. If I remember correctly SourceSafe did automatically hide this window after a source control operation was completed (succesfully). Although every Vault operation ends succesfully (as far as I can tell), the window sometimes remains visible.

I don't know if this is a bug or a feature. Can you tell me?

lbauer · Post by **lbauer** » Tue Jan 18, 2005 8:21 am

I wasn't able to reproduce this when I created a project and added it to source control. The Source Control Status window disappeared on cue. When doing checkins, it hesitated for a moment but still closed.

You said that this happens "sometimes." If you detect a pattern, let us know and we'll investigate further.

davidt · Post by **davidt** » Tue Jan 18, 2005 8:32 am

My observation has always been that if the SCC provider showed messages, VB6 left the results window visible and hid the window otherwise. This is how it worked with SourceSafe, and the behavior with Vault appears to be the same.

Is there an option in Vault to have the SCC provider show messages only when something abnormal happens?

dan · Post by **dan** » Tue Jan 18, 2005 8:56 am

davidt wrote:Is there an option in Vault to have the SCC provider show messages only when something abnormal happens?

There isn't an option like this.

I've noticed that window sometimes goes away and sometimes stays up, and have never been able to figure out a pattern to it. It is a window that Visual Studio puts up, not Vault, so the mystery will have to be solved by someone on worked on VB6 many years ago

lzandman · Post by **lzandman** » Wed Jan 19, 2005 6:15 am

dan wrote:I've noticed that window sometimes goes away and sometimes stays up, and have never been able to figure out a pattern to it. It is a window that Visual Studio puts up, not Vault, so the mystery will have to be solved by someone on worked on VB6 many years ago

I guess I'll just have to live with it then. I don't think I'll be using Visual Studio 6 a lot anymore, so it's not a big problem. For now I'll just deactivate Vault's IDE integration. As I've said before I prefer the use of the Vault client over IDE integration.

davidt · Post by **davidt** » Thu Feb 24, 2005 5:45 pm

We still have a couple projects that we haven't migrated from VSS to Vault, so I was able to observe VSS at work.

The messages dialog appears to have a one-line message area and a multi-line message area. By and large, VSS prints its normal working messages about checking out and checking in to the one-line message area. When it's done, the SCC interface module sees there are no messages in the multiline message area, and automatically closes the window.

Vault generally prints its messages to the multi-line area. So the SCC module sees messages there (where VSS normally only prints for unusual circumstances), and doesn't close the window.

There are a few times Vault doesn't print anything there, such as when you ask to get latest on a file for which you already have the latest version, or undoing checkout on a file that isn't actually checked out. On those occasions, the SCC message dialog disappears on its own.

If it's possible for Vault to choose whether its messages go into the single-line or multi-line area, you might be able to make the dialog autohide more often.

Thanks!