Search

Keyboard binding for Diff.NextDifference ignored by Edward D. Brey

Closed

1
0
Sign in
 to vote
Type: Bug
ID: 777410
Opened: 1/24/2013 8:44:54 AM
Access Restriction: Public
0
Workaround(s)
1
User(s) can reproduce this bug
If you try to create a keyboard binding for "Alt+Down Arrow" on the Difference Viewer window, the binding is ignored.

"Alt+Down Arrow" is the default binding for next difference in WinMerge. It is quite handy because the programmer's right hand is already on the arrow keys to rapidly move between files being diffed. While the default binding of F8 is nicely consistent with the rest of Visual Studio, it's just not as fast for multi-file diffing.
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

Steps to reproduce

1. In Keyboard Options, bind "Alt+Down Arrow" to Diff.NextDifference, specifying to use the new shortcut in "Difference Viewer".

2. Diff two files that have differences. Press "Alt+Down Arrow".

Product Language

English

Operating System

Windows 8

Operating System Language

English

Actual results

The line with focus is moved down.

Expected results

Focus moves to the next difference.
File Attachments
File Name Submitted By Submitted On File Size  
FeedbackReport.zip (restricted) Edward D. Brey 1/25/2013 -
Sign in to post a comment.
Posted by Edward D. Brey on 2/4/2013 at 11:32 AM
The source of the problem turned out to be the Productivity Power Tools extension (http://visualstudiogallery.msdn.microsoft.com/d0d33361-18e2-46c0-8ff2-4adea1e34fef) Move Line Up/Down Commands feature. When it is enabled, it appears to override other keyboard bindings for "Alt+Down Arrow". With the feature off (or the extension disabled), Visual Studio 2012 RTM behaves properly.
Posted by Microsoft on 2/4/2013 at 9:40 AM
Thank you for your patience. Using Visual Studio 2012 RTM, we haven't been able to reproduce the problem internally.

The problem might be related to one of the extensions you have installed. Try to disable all extensions, and validate that the problem does not occur, then start to activate extensions one by one to find out which extension is causing the problem.

If this solution does not help, please update us by reactivating this bug.

Thank you,
Visual Studio Professional - Language Experience team
Posted by Microsoft on 1/27/2013 at 11:12 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Edward D. Brey on 1/25/2013 at 4:29 AM
The Feedback Tool's capture succeeded, but its upload failed; so I zipped up its report files from %localappdata%\VSFeedbackTool\Feedbacks and uploaded them as FeedbackReport.zip.
Posted by Microsoft on 1/24/2013 at 9:35 PM
Thanks for your feedback. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please use Visual Studio 11 Feedback Tool to collect steps while you're repro'ing the issue?

Visual Studio now has an extension called Visual Studio 11 Feedback Tool , available on the VS gallery(http://visualstudiogallery.msdn.microsoft.com/f8a5aac8-0418-4f88-9d34-bdbe2c4cfe72).

The extension allows you to
1.    upload files,
2.    collect trace and dump files
3.    collect steps while you're repro'ing the issue, as well as
4.    SQM logs about VS extensions installed
5.    System details (in DxDiag output)

We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 1/24/2013 at 8:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.
© 2013 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement