views:

55

answers:

2

I'm not sure what could be causing this, but I installed GhostDoc and the default key combination of Ctrl+Shift+D worked as expected for quite some time. Recently it just plain stopped for no known reason (there were updates installed, but none related to .NET or Visual Studio that I'm aware of). Looking under Tools -> Options -> Environment -> Keyboard, I'm still seeing the value mapped to the Tools.SubMain.GhostDoc.DocumentThis command. Although when I try pressing the key combination in the "Press shortcut keys:" textbox it doesn't register it. It registers other Ctrl+Shift+... combinations, just not with D.

Has anybody else experienced this before? Any possible solutions (hopefully not involving resetting all keyboard shortcuts)?

A: 

Are you sure GhostDoc is still working?

Broam
Yes, navigating the menus and clicking on "Document This" still works as expected. I don't suspect it to be GhostDoc related.
Agent_9191
+2  A: 

Is it possible you have another application running that uses the same key combination? It happened to me with Winamp global keys.

Check out this app tough it can't display which app has registered an active hotkey. I haven't tried it, but if it detects current assigned key combinations you could remove running apps to determine which one uses Ctrl + Shift + D. They have an open question on Stack Overflow about determining who has what registered. Some answers there reference other apps that might help you - this, maybe?.

vladhorby
If Shortcuts page in Tools->Options doesn't react to Ctrl+Shift+D anymore, this is almost certainly a global hotkey.
Pavel Minaev
Granted it's more of a SuperUser question, but any ideas how to find what could be trapping it? I launched Key Jedi and it's seeing the key combination while inside Visual Studio. So I'm not sure what could be preventing VS from seeing it.
Agent_9191
Thanks for pointing out the apps. ActiveHotKeys pointed out that something was attached to the combination, but no matter what processes I killed it remained attached. A system reboot (which I had done before anyways) cleared it up.
Agent_9191