Vault and Multi-Edit
Moderator: SourceGear
Vault and Multi-Edit
We use the Vault client from within Multi Edit.
This editor has a standard SCC interface and worked fine.
Until the login profiles were introduced.
Since that moment Vault keeps asking for the login profile.
Depending on the action to perform, it is being asked multiple times.
Ofcourse this is very annoying.
Is there anyone experiencing similar problems
This editor has a standard SCC interface and worked fine.
Until the login profiles were introduced.
Since that moment Vault keeps asking for the login profile.
Depending on the action to perform, it is being asked multiple times.
Ofcourse this is very annoying.
Is there anyone experiencing similar problems
Ofcourse I did that.jeremy_sg wrote:Have you set up one of the profiles to connect automatically? You can do this in the Edit Profiles dialog from the login dialog. Also, you might want to choose a repository to automatically connect to.
That part of the login is very obvious.
The problem is, that Multi Edit probably doesn't see it (anymore...)
In the Vault versions without the login profiles (pre 2.xx) there were no problems at all. So I would really want an option to disable the loginprofiles and use the old login style
Ok. I'm officially confused. I'm going to try to restate your problem to see if I can understand it.
You load up MultiEdit with Vault Integration.
Your connection to Vault is automatically established, because you have a profile with auto-connection
You then perform an operation. You're prompted for login, despite your profile settings.
The GUI client connects automatically, but MultiEdit stubbornly refuses to leave you alone.
You load up MultiEdit with Vault Integration.
Your connection to Vault is automatically established, because you have a profile with auto-connection
You then perform an operation. You're prompted for login, despite your profile settings.
The GUI client connects automatically, but MultiEdit stubbornly refuses to leave you alone.
Yes, that's totally right.
While in the same session of Multi Edit, if I want to check out a file that isn't in a directory that's in the associated directorylist, I am able to browse for the correct project and directory, so the connection is there.
But when the transaction starts, I get the loginscreen, (sometimes more then once), despite of the login profile that is checked to choose it automatically next time.
In a way, the current procedure differs from the one that was used in the pre 2.xx version of the Vault client.
The GUI client has no problems using the profiles.
At first I thought this behaviuour was caused by simultaniousely having Multi Edit and the Gui Client open at the same time, but with the GUI Client closed, I get the same annoying login screen.
While in the same session of Multi Edit, if I want to check out a file that isn't in a directory that's in the associated directorylist, I am able to browse for the correct project and directory, so the connection is there.
But when the transaction starts, I get the loginscreen, (sometimes more then once), despite of the login profile that is checked to choose it automatically next time.
In a way, the current procedure differs from the one that was used in the pre 2.xx version of the Vault client.
The GUI client has no problems using the profiles.
At first I thought this behaviuour was caused by simultaniousely having Multi Edit and the Gui Client open at the same time, but with the GUI Client closed, I get the same annoying login screen.
I found the problem on the login screens in Multi Edit.
It is caused by the slashes in the projectname.
By adding the following lines of code in the ME SCC sourcefile, just below the block with " if ( g_SccPkg == "SourceOffSite" ) {
.....
}
if ( g_SccPkg == "SourceGear Vault" ) {
// Change \\ to /
Jx = 1;
while ( Jx = XPos( "\\", TProjName, Jx ) ) {
TProjName = Str_Ins( "/", Str_Del( TProjName, Jx, 1 ), Jx );
}
}
Apparently Sourcegear puts the slashes the other way around.
I don't know what the standard is for SCC, but this addition workes for me, so problem solved !!!!!
It is caused by the slashes in the projectname.
By adding the following lines of code in the ME SCC sourcefile, just below the block with " if ( g_SccPkg == "SourceOffSite" ) {
.....
}
if ( g_SccPkg == "SourceGear Vault" ) {
// Change \\ to /
Jx = 1;
while ( Jx = XPos( "\\", TProjName, Jx ) ) {
TProjName = Str_Ins( "/", Str_Del( TProjName, Jx, 1 ), Jx );
}
}
Apparently Sourcegear puts the slashes the other way around.
I don't know what the standard is for SCC, but this addition workes for me, so problem solved !!!!!
For anyone using Multi-Edit, please note:
SourceGear Vault does not support integration with Multi-Edit. While some development tools appear to integrate with Vault, there can be unexpected results.
We've had specific reports of file status being incorrect when users used Multi-Edit's Diff, which calls the SCC API. This can lead to files being overwritten rather than merged.
SourceGear Vault does not support integration with Multi-Edit. While some development tools appear to integrate with Vault, there can be unexpected results.
We've had specific reports of file status being incorrect when users used Multi-Edit's Diff, which calls the SCC API. This can lead to files being overwritten rather than merged.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager