| T O P I C R E V I E W |
| Joe Sixpack |
Posted - Oct 13 2006 : 5:36:51 PM
Double clicking an item in the References Results Window fails to open the file and navigate to the item.
Using:
Visual Studio 2003 SP1 in MDI mode
The problem also occurs with Visual Studio 6
A C++ Project
Steps to repeat:
1) Open a cpp file with a function that is referenced in other cpp files.
2) Double-click the function name to highlight it and select VAssistX->Find References... from the VS main menubar.
3) The VA Find References Result window opens and eventually populates with a list of the references.
4) Double click one of the entries, the file with the reference opens or is brought to the foreground and the referenced item is highlighted.
5) Close the file just opened or brought to the foreground.
6) Double-click another entry in the VA Find References Results window.
7) BUG: Nothing happens.
The VA Find References Results window works as long as you don't close any of the files previously opened by double-clicking an entry. As soon as you close one of the referenced files it stops working. Repeating step 1-3 to re-find the references fixes the problem at the expense of having to wait for the window to repopulate.
VA_X.dll file version 10.3.1534.0 built 2006.09.02
VAOpsWin.dll version 1.3.3.6
VATE.dll version 1.0.5.8
DevEnv.exe version 7.10.6030.0
msenv.dll version 7.10.6030.0
Font: Courier New 13(Pixels)
Comctl32.dll version 5.82.2900.2982
Windows XP 5.1 Build 2600 Service Pack 2
2 processors
|
| 4 L A T E S T R E P L I E S (Newest First) |
| support |
Posted - Oct 30 2006 : 12:23:36 AM
Case 2365 is fixed in 1540. |
| jpizzi |
Posted - Oct 14 2006 : 01:40:15 AM
Thank you for the excellent detective work.
case=2365
*feline changed bug number* |
| Joe Sixpack |
Posted - Oct 13 2006 : 7:07:30 PM
Ok, the problem occurs when VA Find References Results window is at the top of the Z-order and automatically gets activated. For example follow these steps:
1) Populate the VA Find References Results window by finding a reference.
2) Select Windows->Close All Documents from the main menubar.
3) Open the VA Find References Results window by using a custom toolbar button assigned to VAssistX.Find References Results command. The VA Find References Results window is automatically activated.
4) BUG: References cannot be accessed either by double clicking or using the Find Next/Prev By Context commands.
5) Now open a document by selecting File->New->File>General->Text File->Open from the main menubar. An empty Text document becomes the active window.
6) Click the VA Find References Results window, it is "manually" activated. Now double-clicking the references works, click a reference and the file opens.
7) Close the file with the reference in it. This causes the VA Find References Results window to automatically be activated. Now double-clicking a reference is broke.
8) Click the new text file created in step 5.
9) Click the VA Find References Results window. Now double clicking the references works again since the window was manually activated.
In Summary when the Click the VA Find References Results window is broke clicking any other mdi child window and manually clicking back to the VA Find References Results window fixes the problem. I suspect you are not getting an Activate or SetFocus message you are expecting.
Note that this means the VA Find References Results window does not work when all the other windows are closed preventing the common process of Find References, Close All Documents, Navigate to each reference. This is the case regardless of whether the window is docked or an MDI child. Also, in step 6, double-clicking a reference works but the Find Next/Prev By Context commands are still grayed out. |
| Joe Sixpack |
Posted - Oct 13 2006 : 6:16:11 PM
Here some newly discovered info on the bug.
1) When the window stops working the Find Next By Context and Find Previous By Context commands are grayed out.
2) Closing the VA Find References Results Window and reopening it by customizing a toolbar with the VAssistX.Find References Results command a clicking it, fixes the problem. A much more palatable workaround than re-finding the references.
3) If I change the state of the VA Find References Results window to Dockable the problem does not occur. In other words the problem occurs when the window is a non-dockable MDI child, it does not occur if it is floating or docked. |
