Resharper 1.5<->2.0 hotkeys inconsistency

I've just installed R#er build 203 on VS2003.

First things I noticed (comparing to v1.5):
1) F2/ShiftF2 (Next/Prev Error) become F12/ShiftF12
2) Shift+F6 (Rename) become F2
3) ShiftTab (prev element in templates) become CtrlTab (disabling standard windows navigation)

First 5 minutes I felt paralyzed until I managed to remap keyboard to the old keystrokes... =)

Was there any reason to move default map for so frequently used keys?

Thanks.

P.S. Does anyone know the way to enter Shift+Tab in Tools->Options->Keyboard dialog? Stupid thing selects previous control... 8)

9 comments
Comment actions Permalink

The Shift-Tab thing is a bug that should be fixed in the next version.

There is no way to map Shift+Tab in the dialog. The only work-around to get
it back that I know if is to reset the keymap completely to "default
settings", and then re-enable Resharper to get its keystrokes back (assuming
you go back to 1.5 ... if you're at 2.0 still, you'll lose Shift+Tab again).


"Chepel" <no_mail@jetbrains.com> wrote in message
news:16394351.1123626187102.JavaMail.itn@is.intellij.net...

I've just installed R#er build 203 on VS2003.

>

First things I noticed (comparing to v1.5):
1) F2/ShiftF2 (Next/Prev Error) become F12/ShiftF12
2) Shift+F6 (Rename) become F2
3) ShiftTab (prev element in templates) become CtrlTab (disabling
standard windows navigation)

>

First 5 minutes I felt paralyzed until I managed to remap keyboard to the
old keystrokes... =)

>

Was there any reason to move default map for so frequently used keys?

>

Thanks.

>

P.S. Does anyone know the way to enter Shift+Tab in
Tools->Options->Keyboard dialog? Stupid thing selects previous control...
8)



0
Comment actions Permalink

Chepel,

The bug with overriding Shift+Tab is fixed in the upcoming build. You may
enter the shortcut in VS dialog, but in the scope TEXT EDITOR only. Why it
is not possible in global, I don't know :)

The main idea of mapping some actions to another shortcuts was that such
mapping more compliant with default VS keymapping. I'm not sure, whether it
was a good idea or not, but I learned to use this new scheme within a couple
of days.

--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

That's great for new people coming in, but maybe in upgrade situations, it
should leave things as they were, or at least give an option? Lots of
developers don't like to find their keys suddenly and quietly remapped, or
have change forced on them. Many developers are creatures of habit and
might not care to relearn things. Just a thought.

"Sergey V. Coox" <qx@intellij.com> wrote in message
news:ddce64$jms$1@is.intellij.net...

Chepel,

>

The bug with overriding Shift+Tab is fixed in the upcoming build. You may
enter the shortcut in VS dialog, but in the scope TEXT EDITOR only. Why it
is not possible in global, I don't know :)

>

The main idea of mapping some actions to another shortcuts was that such
mapping more compliant with default VS keymapping. I'm not sure, whether
it was a good idea or not, but I learned to use this new scheme within a
couple of days.

>

--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"



0
Comment actions Permalink

Thanks for the "TextEdit scope" suggestion. I would never think of this one... =)

Regarding other keys... It doesn't really matter for me of how the keys are actually mapped as far as I can change it anyway. =)

But in my opinion new F12 key for next/prev error is not a good choice because you have to press it with your left hand while your right hand is on the "cursor arrows" keys. With F2 it was so much easier... Am I right? Or I'm the only one who does it? ;)

Regards,
Chepel

0
Comment actions Permalink

Moreover F12 is used in VS2005.

Yuriy

Thanks for the "TextEdit scope" suggestion. I would never think of
this one... =)

Regarding other keys... It doesn't really matter for me of how the
keys are actually mapped as far as I can change it anyway. =)

But in my opinion new F12 key for next/prev error is not a good choice
because you have to press it with your left hand while your right hand
is on the "cursor arrows" keys. With F2 it was so much easier... Am I
right? Or I'm the only one who does it? ;)

Regards,
Chepel



0
Comment actions Permalink

And F2 is the standard Windows shortcut for renaming that is used in many
applications (VS including).

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

Moreover F12 is used in VS2005.

Yuriy

>> Thanks for the "TextEdit scope" suggestion. I would never think of
>> this one... =)
>>
>> Regarding other keys... It doesn't really matter for me of how the
>> keys are actually mapped as far as I can change it anyway. =)
>>
>> But in my opinion new F12 key for next/prev error is not a good
>> choice because you have to press it with your left hand while your
>> right hand is on the "cursor arrows" keys. With F2 it was so much
>> easier... Am I right? Or I'm the only one who does it? ;)
>>
>> Regards,
>> Chepel


0
Comment actions Permalink

Well I'm spoiled with FAR, so for me Shift+F6 is a natural way of renaming things around... ;)

And F2 is the standard Windows shortcut for renaming that is used in many
applications (VS including).

0
Comment actions Permalink

And F2 is the standard Windows shortcut for renaming that is used in many
applications (VS including).


Yeah, but how many times do you do "Rename" in VS? I think Rename is not
such a popular action to be mapped to F2.
If that would be the case, why do we ever use "F10" ?? Then the default
windows behaviour for F10 is "Menu" same as Alt. Just that VS thought it's
more important to use F10 for other actions than "Menu".

Please give the option to NOT override the keyboard scheme during setup. I
hate to have my keys remapped.

Corneliu.



>

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

>
>> Moreover F12 is used in VS2005.
>>
>> Yuriy
>>
>>> Thanks for the "TextEdit scope" suggestion. I would never think of
>>> this one... =)
>>>
>>> Regarding other keys... It doesn't really matter for me of how the
>>> keys are actually mapped as far as I can change it anyway. =)
>>>
>>> But in my opinion new F12 key for next/prev error is not a good
>>> choice because you have to press it with your left hand while your
>>> right hand is on the "cursor arrows" keys. With F2 it was so much
>>> easier... Am I right? Or I'm the only one who does it? ;)
>>>
>>> Regards,
>>> Chepel
>



0
Comment actions Permalink

>>Yeah, but how many times do you do "Rename" in VS? I think Rename is not
>>such a popular action to be mapped to F2.

I use rename about once every 2 minutes! I think it should be compulsory to use it at least once an hour ;) First-choice variable and method names are never perfect. Refactor, refactor, refactor...

On the issue of changing the keyboard scheme: I agree, the option of not changing the existing keyboard scheme during setup would be a good idea.

0

Please sign in to leave a comment.