Resetting keyboard shortcuts

Hello,

Why is it that ReSharper resets keyboard shortcuts every time you
upgrade to a new version?

To make sure that all the newly-introduced keyboard shortcuts are property
assigned. To fix the broken shortcuts, also. It is hard to track which shortcuts
are just missing, and which were removed intentionally by the user, so R#
would overwrite all of them.

Luckily I've gotten used to it and I export
my keyboard settings before I upgrade and then reimport them after,
but coupled with bugs in import/export keyboard settings this is
incredibly annoying behavior. Also, the ReSharper one time
initialization seems to do this too, so every time I install a plugin
I have to fix my keyboard settings.

Usually it's enough to export just once and then reimport the settings after
a one-time-init, which does not take any significant time. That scenario
was not uncommon among our team, also. Starting with R# 3.0, we have introduced
the new keyboard scheme which is “Visual Studio friendly”, which means it
would not conflict with the usual VS shortcuts for most actions. Using that
scheme works out most of the keyboard shortcut problems. It can be switched
at Options / Environment / General.

If that keyboard scheme is still too descructive for your settings, there's
one more trick, as described in the news://news.intellij.net/dc0986bf671d08c98bcc0871c19f@news.intellij.net
message.

“
Alternatively, you could find the “KeyboardScheme” setting in the R#'s “UserSettings.xml”
file under the Roaming Application Data folder, and change its value to “None”,
but this way you'll never see the newly-introduced keyboard shortcuts, that's
why the import/export approach is recommended.
”

—
Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”

Almost... except that ReSharper still removes the keybinding for F6, which a
standard Windows keybinding for switching panes. If I remember correctly,
the keybinding for Shift+F6 remains intact.

"Serge Baltic" <baltic@intellij.net> wrote in message
news:dc0986bf6ad0e8c9a8197c5b276f@news.intellij.net...

Hello,

>
>> Why is it that ReSharper resets keyboard shortcuts every time you
>> upgrade to a new version?
>

To make sure that all the newly-introduced keyboard shortcuts are property
assigned. To fix the broken shortcuts, also. It is hard to track which
shortcuts are just missing, and which were removed intentionally by the
user, so R# would overwrite all of them.

>
>> Luckily I've gotten used to it and I export
>> my keyboard settings before I upgrade and then reimport them after,
>> but coupled with bugs in import/export keyboard settings this is
>> incredibly annoying behavior. Also, the ReSharper one time
>> initialization seems to do this too, so every time I install a plugin
>> I have to fix my keyboard settings.
>

Usually it's enough to export just once and then reimport the settings
after a one-time-init, which does not take any significant time. That
scenario was not uncommon among our team, also. Starting with R# 3.0, we
have introduced the new keyboard scheme which is “Visual Studio friendly”,
which means it would not conflict with the usual VS shortcuts for most
actions. Using that scheme works out most of the keyboard shortcut
problems. It can be switched at Options / Environment / General.

>

If that keyboard scheme is still too descructive for your settings,
there's one more trick, as described in the
news://news.intellij.net/dc0986bf671d08c98bcc0871c19f@news.intellij.net
message.

>

“
Alternatively, you could find the “KeyboardScheme” setting in the R#'s
“UserSettings.xml” file under the Roaming Application Data folder, and
change its value to “None”, but this way you'll never see the
newly-introduced keyboard shortcuts, that's why the import/export approach
is recommended.
”

>

—
Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”

>

Hello,

Almost... except that ReSharper still removes the keybinding for F6,
which a standard Windows keybinding for switching panes. If I remember
correctly, the keybinding for Shift+F6 remains intact.

Cannot confirm. The Visual Studio Friendly keyboard layout does not reassign
the F6 key. What you see could be some remainders of a previous version.

—
Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”