[319] Resharper Shortcut Conflict

The Resharper Shortcut Conflict window seems to reappear each time I install
a new version of R#, is this expected? It's appearing for basic keypresses
like CTRL+Arrow keys.

Also, as commented in RSRP-31976
(http://www.jetbrains.net/jira/browse/RSRP-31976), R# will only persist the
choice I select in the dialog box when I close VS2005. This is a pain since
I keep several instances of VS2005 open at once, and have to close all other
instances before making a configuration change in R#.


3 comments
Comment actions Permalink

Dag,

On install resharper resets all the shortcuts to the initial state. It looks
like it restores default shortcuts while uninstall and then detects
shortcuts conflicts during
installation process. We override ctrl+Arrow shortcuts to enable navigation
to the next/previous word part (which is not provided by VS). Besides that,
our architecture does not support sharing information between different
instances of Visual Studio still.
--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

Hello Sergey,

installation process. We override ctrl+Arrow shortcuts to enable
navigation
to the next/previous word part (which is not provided by VS). Besides


CtrlArrow and CtrlShift+Arrow shortcuts have always been standard navigation/select shortcuts in VS, and indeed Windows UI compliant editors, and still are. That is why there is a conflict between R# and VS in this particular point. Both are mapping for the same function; this is a redundancy we can do without.

If for some reason this is not stadard across all locales, then R# needs to either check locale information or provide one checkbox in 'Options' to disable R# overwriting editor navigation for these shortcuts.

I have provided screens showing VS default mapping for CtrlRight Arrow and the Shortcut Conflict dialog for CtrlLeft Arrow

Attachment not added (general error): "VS Default.png"

0
Comment actions Permalink

If you let R# take care of CTRL+arrow keys, and enable Use "CamelHumps" in
Reshaper (Options -> Editor) you'll see the difference.

Not sure if there's other improvements? It would (perhaps?) be nice if the
reset shortcut keys button asks you if you want to replace VS bindings
instead of showing a popup. I know it's only displayed once for each
install (unless you forget to click the checkbox), but popups are very
intrusive when you're working in a text editor imho.


"Matthew Moody" <mgmoody@nospam.com> wrote in message
news:987a13602e6b58c8e66bfea3d596@news.jetbrains.com...
Hello Sergey,

installation process. We override ctrl+Arrow shortcuts to enable
navigation
to the next/previous word part (which is not provided by VS). Besides


CtrlArrow and CtrlShift+Arrow shortcuts have always been standard
navigation/select shortcuts in VS, and indeed Windows UI compliant editors,
and still are. That is why there is a conflict between R# and VS in this
particular point. Both are mapping for the same function; this is a
redundancy we can do without.

If for some reason this is not stadard across all locales, then R# needs to
either check locale information or provide one checkbox in 'Options' to
disable R# overwriting editor navigation for these shortcuts.

I have provided screens showing VS default mapping for Ctrl+Right Arrow and
the Shortcut Conflict dialog for Ctrl+Left Arrow


0

Please sign in to leave a comment.