Some keys stops responding

I am using Reshaper 2.0.266.2 on VS2003. Some times, some od the keyboard keys stop responsing.

Symtomps:
- alphanumeric keys works ok
- space works OK
- backspace, delete, arrow keys do not work
- The status line shows "Searching c:\....(somefile...", and the binocular icon is animated (as when search in files is doing some work). The name of the file does not change,
- I can not use ALTxxx shots cuts (like AltF to open File Menu)

My idea some invisible popup window is stealing the keys.

The only known way to et out of this mess is to restart VS.NET.

Any ideas?

Thanks,
matej

5 comments
Comment actions Permalink

same problem here

0
Comment actions Permalink

Same problem for me. After installing Resharper 2.5 (326.1) I cannot use the arrow keys/backspace/delete in the text editor. Very annoying indeed.

I did see error messages about key shortcuts during the install but as I don't use keyboard shortcuts I was unconcerned - until it did this. I've tried 'Reset' under Tools->Options->Keyboard but to no effect.

Matt

0
Comment actions Permalink

Some more details:

When I try to run ReSharper->Options->Reset Shortcuts I get the dialogue box:

"Some shortcuts may not be set properly because current keyboard scheme is read only. Change keyboard scheme and rerun reset shortcuts."

After clicking OK I get the dialogue box:

"Cannot set ReSharper keyboard shortcuts. If you are using the default keyboard mapping scheme, please make a copy of it (Tools|Options|Environment|Keyboard settings) and press the ReSharper->Options->General->Reset Shortcuts button. Details:Error HRESULT E_FAIL has been returned from a call to a COM component."

I just want my delete key back ... can anyone suggest a workaround please?

0
Comment actions Permalink

problem is still there since r# 1.0, when will this be fixed?

0
Comment actions Permalink

Hello Carsten,

do you mean you're getting the same error message box? Thank.


Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


problem is still there since r# 1.0, when will this be fixed?



0

Please sign in to leave a comment.