All,
On a couple of machines we installed have encountered the Check-In Dialogs to be invisible. They are there and the buttons can be correctly selected (tabbing the correct number of times and pressing enter). You cannot see them, altho the cursor does follow the tab order around the screen.
This is from within VS 2005 Team Suite attached to TFS. These machines do not seem to share much extra software in common and do not have lots of 3rd party software loaded.
We are currently trying to reproduce this issue, but I am wondering if others have encountered this affect and if there is a solution available. I have searched the archives but have not found a similar issue... yet.
Thanks in advance.
James
Help: Invisible Dialog on Check-in
RCS300
The dialog is most likely offscreen or partially offscreen. Modal version control dialogs have their location and dimension saved in a cache file. If you switch between single and dual monitors regularly (like between the office and home), it is possible that a dialog previously shown on a secondary monitor is showing offscreen when switched to a single monitor setup. If this is truly a location caching/restoring problem, you can try deleting the UI cache file which forces the dialogs to be initially shown at their default location. The cache file is located at:
XP: C:\Documents and Settings\<UserName>\Local Settings\Application Data\Microsoft\Team Foundation\1.0\Cache\UISettings.Config
Vista: H:\Users\<UserName>\AppData\Local\Microsoft\Team Foundation\1.0\Cache\UISettings.Config
Hope this helps.
-Tan
Toon Nijland
In the case I have seen a dual monitor systems caused the dialog to display off the visible horizon. When clearing the extend desktop flag over the second monitor the dialog displayed center screen. After re-checking the extend desktop flag while the check-in dialog was displayed it seemed to work ok.
Still suspect some bug in VSTS somewhere since other programs don't exhibit the same issue. Even other dialogs in VSTS don't do this. Just the check-in dialog per our experiences.
Tom bernard
Hi:
That is interesting. I have asked our test team to investigate and see if we can find the bug. James did the above fix the problem
thanks, mario