Home Dashboard Directory Help

Horizontal scroll with mouse wheel does not work with Microsoft Explorer Mini Mouse in VS2010 Text Editor by T. Webster


 as Not Reproducible Help for as Not Reproducible

Sign in
to vote
Type: Bug
ID: 635995
Opened: 1/13/2011 2:13:44 PM
Access Restriction: Public
User(s) can reproduce this bug


I have VS2010 Professional on Windows XP SP3, and have the Microsoft Explorer mini mouse. and horizontally scrolling with the mouse wheel works fine with in Solution Explorer, Object Browser, and applications like Adobe Reader. However, in the Text Editor of the IDE the mouse cannot perform horizontal scrolling. Is this a known bug, and is there a workaround or hotfix for this?

I have already reported this on the MSDN community forums here:

The moderator Victor_Chen has forwarded me to seeking help here at Connect.
Sign in to post a comment.
Posted by T. Webster on 2/10/2011 at 1:50 PM
This issue is that the horizontal scroll bar IS visible in the Visual Studio 2010 text editor tab window, yet it still does not scroll horizontally when I use the Microsoft Explorer Mini Mouse middle tilt wheel. I have used Microsoft Spy++ to look at messages received by the Visual Studio 2010 window, and Spy++ does not seem to be report any messages from the mouse when I perform a horizontal scroll action on the middle tilt wheel, however it does show messages if I perform a vertical scroll action. In SQL Server 2008 Management Studio, it does respond to horizontal scrolling. Do you know why this is?
Posted by Microsoft on 2/2/2011 at 11:13 PM
Hi T. Webster,

I apologize for the inconvenience. We are aware of one issue with horizontal mouse wheel scrolling where the scroll messages are being sent to a tool window instead of the main editor. (E.g. if you have find results up). In some cases, there is no visible change because the window doesn't have a horizontal scrollbar. Closing the window should cause the editor to scroll horizontally. If this is your issue then we have fixed this for the next major version of Visual Studio.

We have received other reports that are different than this one but we have been unable to reproduce it or determine what is causing the issue. If this is the case for you, please let us know and we'll see if there is an option to investigate this further.

Posted by Microsoft on 1/13/2011 at 3:15 PM
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.