| T O P I C R E V I E W |
| kinook |
Posted - Jan 19 2006 : 07:44:31 AM
When invoking the VAssistX.GotoImplementation command (mine is mapped to Alt+G), if the method under the cursor is overridden, a context menu is displayed with the different overrides. This context menu is positioned at the mouse cursor rather than the caret position in the editor. For keyboarders working w/ multiple monitors, this can be rather annoying (for a while I thought that VAssist was ignore my keystroke, but then I noticed the menu was coming up on my non-primary monitor where the mouse cursor happened to be, and now that I know, it's still unproductive to scan around the monitors to find it).
VA_X.dll file version 10.2.1440.0 built 2006.01.17
Licensed to:
VA X:
VA.NET 7.1:
VA 4.1:
VAOpsWin.dll version 1.3.2.0
VATE.dll version 1.0.4.12
DevEnv.exe version 7.10.3077.0
msenv.dll version 7.10.3077.0
Font: Andale Mono 13(Pixels)
Comctl32.dll version 5.82.2900.2180
WindowsNT 5.1 Build 2600 Service Pack 2
Single processor
Platform: Win32
Stable Includes:
C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\include;
C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\atlmfc\\include;
C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\PlatformSDK\\include\\prerelease;
C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\PlatformSDK\\include;
C:\\Program Files\\Microsoft Visual Studio .NET 2003\\SDK\\v1.1\\include;
G:\\src\\boost_1_33_0;
Library Includes:
C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\atlmfc\\src\\mfc;
C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\atlmfc\\src\\atl;
C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\crt\\src;
Other Includes:
|
| 4 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Jan 22 2006 : 2:12:52 PM
we try to keep VA options to an absolute minimum, since each additional option causes a lot of extra work, more than you might expect. still, as a keyboard centric user myself i like this idea. i will ask support and see what they think. there is not a lot of point in putting in a feature request that stands no real chance. |
| kinook |
Posted - Jan 20 2006 : 10:45:05 AM
Normally, you can honor the method used to invoke the context menu, and position near the mouse cursor if invoked via the mouse and near the caret position if invoked via the keyboard. I can see where this might be more difficult with the add-in running in the context of the IDE and possibly not being privy to that information. Another possibility would be a VAssist option as to where to position it (near the caret or the mouse cursor). |
| feline |
Posted - Jan 19 2006 : 2:27:20 PM
speaking as a keyboard user with dual monitors i find the best solution is to "keep" the mouse cursor over the main IDE title bar. this way i know where to look when i issue alt-g, and the mouse is in a known position when i do have to drag it down to do something *sigh* |
| support |
Posted - Jan 19 2006 : 11:48:03 AM
We appreciate your position but the behavior is by design. We're not saying it's right or perfect; we just know we're doing it.
We used to open the menu at the caret but if we recall correctly, people didn't like the fact they had to hunt for their mouse to make a selection.
We'll see if we can think of a reasonable change. |
