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)

Same here on a Medion MD-98200 notebook with Synaptics touchpad.
I'm not able to scroll in any WPF ScrollViewer, including the VS2010 source view. This happens for both .NET 3.5 SP1 and .NET 4.0 Beta 1 apps.

I tried the latest official driver from the Synaptics site (Synaptics_Driver_v10_1_8_Vista32.exe) as well as a "synaptics_v12.2.11.0.exe" which can be found on http://www.laptopvideo2go.com/forum/index.php?showtopic=15103
Both have the same problem.

I'm also having the same problem. Toshiba Satellite A135-S4427. Syntaptics driver 6.4. I've tried adjusting all the scroll settings and all I can get it to do is scroll the entire page. I will kick off the scroll and after a few seconds it will jump to the bottom of the editor window.

On top of this the keyboard arrows are also having issues in XAML. I will hit down and it will go down a few lines and then refuse to go, after that I must click the next line or use the right arrow to get to it.

Hi Sven (and Daniel and tagnarth),

Thank you for reporting (and confirming) this issue. We have been able to reproduce this on several laptop touchpads and hope to fix it for the final release of Visual Studio 2010. I've assigned this to a developer on the VS Editor team for investigation, and I'll post an update here when we have more information to share.

Thanks again for trying VS 2010 Beta1 and posting your feedback!

Brittany Behrens
Program Manager, VS Platform
http://blogs.msdn.com/vseditor

Hello again,

After some initial investigation, the Editor development team found that this is an issue that should be handled by the WPF team. They'll pick up the investigation and fixing of this bug from here.

Thanks again,
Brittany

This might be of help to the WPF team... in its early days, Google Chrome found and tackled a similar issue with Synaptics touchpads and scrolling not working. Maybe it would give some insight?

http://code.google.com/p/chromium/issues/detail?id=4

The WPF team has investigated this issue and found it to be by design. In WPF we do listen to WM_MOUSEWHEEL (that is the message raised by TouchPad scroll action) and raise VerticalMouseWheel events in response. The WPF ScrollViewer also responds to these events. We tried this in the VS code editor and found that as long as mouse is over the area of the code editor the mouse wheel messages are honored and scrolling does happen. In my understanding the expectation, though, is that if keyboard focus is in the code editor we want it to scroll in response to mouse wheel (independent of where the mouse is). In WPF we send mouse wheel messages to the mouse over/captured element, not to the element with keyboard focus. A workaround for this does exist and the WPF team has assigned the bug back to VS with suggestions for implementing the workarounds.

Thanks,
Samantha
Program Manager, WPF Tree Services & Controls

The WPF team has investigated this issue and found it to be by design. In WPF we do listen to WM_MOUSEWHEEL (that is the message raised by TouchPad scroll action) and raise VerticalMouseWheel events in response. The WPF ScrollViewer also responds to these events. We tried this in the VS code editor and found that as long as mouse is over the area of the code editor the mouse wheel messages are honored and scrolling does happen. In my understanding the expectation, though, is that if keyboard focus is in the code editor we want it to scroll in response to mouse wheel (independent of where the mouse is). In WPF we send mouse wheel messages to the mouse over/captured element, not to the element with keyboard focus. A workaround for this does exist and the WPF team has assigned the bug back to VS with suggestions for implementing the workarounds.

Thanks,
Samantha
Program Manager, WPF Tree Services & Controls

Hi Samantha,

the trackpad scroll does not work even if the mouse pointer is in the code window.

I do not expect touchpad scrolling of the source code to work when the mouse is outside of the source window but when it is inside the code window.

Do you say that in your build of VS2010 the scrolling of the source code with the touchpad does work?

Thanks,
Sven

Hello Sven,

I just wanted to send you an update to let you know that a developer on the Visual Studio Platform Shell team is now investigating this bug with the touchpad scrolling in the code window. We'll let you know the results of this investigation.

Thanks,
Suzanne Hansen, Program Manager, Visual Studio Platform Shell Team

This same issue is present on every laptop/netbook I have tested with a touch pad and scroll area. Sometimes it works slightly, where quick scrollup/down movements might make it jump up or down a bit. But certainly not useable.

I've investigated the issue somewhat and tried a few workarounds with no success. It is a WPF issue as already mentioned, it happens in every ScrollViewer. I even went so far as to handle the WM_MOUSEWHEEL event and push WPF mousewheel events. However, the ScrollViewer never gets these messages on a touchpad enabled system - even with a scrollwheel mouse plugged in to it. (Works on a regular PC perfect).

I can push WPF scroll wheel events in reaction to another action (such as keydown, mouse click, etc) and the scrollviewer will scroll as expected.

However, when these events are pushed because of a WM_MOUSEWHEEL message or during the user scrolling the touch pad, it never seems to work - ie I used PostMessage to send a different event and than pushed the WPF scroll event from there, still didn't work. I think the WPF input system is somehow detecting the touch scrolling action and simply discarding it when I push the MouseWheell RoutedEvent.

Very odd issue, with no way to workaround... except maybe using custom scrollviewer's everywhere, with a custom method to manually scroll the scroller.

ThikPad Trackpoint middle-button scrolling also does not work for me in any WPF application at all. Please fix this problem, because it really is the most usefull feature that we can not be using now.

I also have this issue... still no fix, 4 months later.

Windows 7 and Vista's OWN PEN FLICKS do not work. What is going on... Do you people actually want us to grab the scrollbar every time we want to scroll? Why do we have scrollwheels then.