4.1 CheckIn Question / Comments
Moderator: SourceGear
4.1 CheckIn Question / Comments
VS2008 with the Enhanced Client
1. Is there any way to surpress the dialog box that appears when checking in a file? I can see this dialog appearing if comments are required but I don't have the option selected. There is no option to hide this dialog listed under the Command Dialogs settings in the Vault Options Settings.
2. I can't seem to get any of the CheckIn Silent keybord shortcuts working from Tools / Options / Environment / Keyboard.
3. Right clicking while in the code editing window used to bring up a menu that included CheckIn. Now that is on a Vault sub-menu. Just an extra step. Would be nice to list Vault Checkin and then the Vault Sub Menu with the other options on it.
4. The Check In Progress dialog box is badly clipped (the bottom is missing and cuts the progress bar) when used on a high DPI set monitor. Display Settings / Settings / Advanced / DPI setting. Looks fine at 96 DPI but is clipped at 120 DPI on windows Vista. Purely cosmetic.
Sorry I didn't point these out before you shipped.
-Andy
1. Is there any way to surpress the dialog box that appears when checking in a file? I can see this dialog appearing if comments are required but I don't have the option selected. There is no option to hide this dialog listed under the Command Dialogs settings in the Vault Options Settings.
2. I can't seem to get any of the CheckIn Silent keybord shortcuts working from Tools / Options / Environment / Keyboard.
3. Right clicking while in the code editing window used to bring up a menu that included CheckIn. Now that is on a Vault sub-menu. Just an extra step. Would be nice to list Vault Checkin and then the Vault Sub Menu with the other options on it.
4. The Check In Progress dialog box is badly clipped (the bottom is missing and cuts the progress bar) when used on a high DPI set monitor. Display Settings / Settings / Advanced / DPI setting. Looks fine at 96 DPI but is clipped at 120 DPI on windows Vista. Purely cosmetic.
Sorry I didn't point these out before you shipped.
-Andy
I can comment on your second question. Those keyboard shortcuts are specific to MSSCCI clients, so I'm not surprised that they don't work with the enhanced client. We'll investigate making similar shortcuts available for the enhanced client, but I can't speculate as to when that might show up in a release.
Ian Olsen
SourceGear
SourceGear
Ian,
Other anoyances: when I check in a file inside of VS with the classic client, it saves the file. The enhanced client does not. I have to acknoledge the save dialog, then the check in dialog and I have to click on the ok button. no way to get there via the keyboard. lots of extra steps. yuk!
I am sticking with the classic client for now.
Other anoyances: when I check in a file inside of VS with the classic client, it saves the file. The enhanced client does not. I have to acknoledge the save dialog, then the check in dialog and I have to click on the ok button. no way to get there via the keyboard. lots of extra steps. yuk!
I am sticking with the classic client for now.
These concerns will be addressed for the 4.1.1 release. Specifically:
1) You can assign keyboard shortcuts for any of the enhanced client commands. This is possible in 4.1.0, but it's difficult to differentiate between the MSSCCI commands and the Enhanced Client commands. 4.1.1 just adds some text so you can differentiate them. However, the check in command listed in 4.1.0 works only on your current selection, so 4.1.1 will also add a commit all key binding (which you have to assign to use), so you can, with one keystroke, get a commit dialog with everything in the solution that's changed.
2) The save prompt is being removed. We'll save silently before any command that requires a save. As you pointed out, this is how MSSCCI clients behave and is no different than, for example, saving silently before a build.
In addition, we're adding a toolbar for the Enhanced client. People who got used to using MSSCCI's toolbar won't have to give that up in the Enhanced Client.
1) You can assign keyboard shortcuts for any of the enhanced client commands. This is possible in 4.1.0, but it's difficult to differentiate between the MSSCCI commands and the Enhanced Client commands. 4.1.1 just adds some text so you can differentiate them. However, the check in command listed in 4.1.0 works only on your current selection, so 4.1.1 will also add a commit all key binding (which you have to assign to use), so you can, with one keystroke, get a commit dialog with everything in the solution that's changed.
2) The save prompt is being removed. We'll save silently before any command that requires a save. As you pointed out, this is how MSSCCI clients behave and is no different than, for example, saving silently before a build.
In addition, we're adding a toolbar for the Enhanced client. People who got used to using MSSCCI's toolbar won't have to give that up in the Enhanced Client.
Ian Olsen
SourceGear
SourceGear
Ian, Great news.
Thanks for adressing these issues. Any idea when we might see an update? My employer is looking to purchase 60ish licenses and I think it is the type of environment that is going to be difficult to install timely updates once we get going. I would rather wait a bit before we roll it out if we will see the update in the short term. Also, please let me know if you need some beta testing.
Thanks again, Andy
Thanks for adressing these issues. Any idea when we might see an update? My employer is looking to purchase 60ish licenses and I think it is the type of environment that is going to be difficult to install timely updates once we get going. I would rather wait a bit before we roll it out if we will see the update in the short term. Also, please let me know if you need some beta testing.
Thanks again, Andy
I understand. Allowing a completely silent check in is worth consideration, but not something we can deliver in 4.1.1.
One other thing I forgot to mention: we'll also add a keyboard shortcut to submit the commit dialog from the comment text box. When the dialog comes up, the comment box has focus: pressing enter inserts line breaks rather than submitting. CTRL-Enter from the comment box, in 4.1.1, will submit the dialog. So if you assign CTRL-Shift-C to the commit all command, you can quickly commit your changes with CTRL-Shift-C, then CTRL-Enter, without ever reaching for the mouse.
We haven't yet announced a date for 4.1.1, but it won't require a server upgrade. So people who care to update their clients, can, without a massive synchronization effort.
If you'd like a pre-release version of the 4.1.1 client, email me (using the button below) and I can probably make one available with these changes later this week.
Thanks for the great feedback.
One other thing I forgot to mention: we'll also add a keyboard shortcut to submit the commit dialog from the comment text box. When the dialog comes up, the comment box has focus: pressing enter inserts line breaks rather than submitting. CTRL-Enter from the comment box, in 4.1.1, will submit the dialog. So if you assign CTRL-Shift-C to the commit all command, you can quickly commit your changes with CTRL-Shift-C, then CTRL-Enter, without ever reaching for the mouse.
We haven't yet announced a date for 4.1.1, but it won't require a server upgrade. So people who care to update their clients, can, without a massive synchronization effort.
If you'd like a pre-release version of the 4.1.1 client, email me (using the button below) and I can probably make one available with these changes later this week.
Thanks for the great feedback.
Ian Olsen
SourceGear
SourceGear