Bug 288 - Synaptics touchpad scrolling doesn't work on in Windows
Summary: Synaptics touchpad scrolling doesn't work on in Windows
Status: RESOLVED NORESPONSE
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: 2.6 Beta 3
Hardware: PC Windows
: Low enhancement
Target Milestone: ---
Assignee: Mike Krüger
URL:
Depends on:
Blocks:
 
Reported: 2011-08-12 21:53 UTC by John Costella
Modified: 2013-12-05 18:35 UTC (History)
4 users (show)

Tags: scroll text editor touchpad gtk
Is this bug a regression?: ---
Last known good build:


Attachments
Scroll cursor (45.15 KB, image/jpeg)
2011-08-23 18:30 UTC, John Costella
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NORESPONSE

Description John Costella 2011-08-12 21:53:16 UTC
MonoDevelop 2.6 beta 3 on Windows 7. All Windows Updates applied.

Either single-finger (right side) or double-finger scrolling on the touchpad shows the standard scrolling mouse cursor, but the code window in the text editor doesn't scroll.

Scroll wheel on an external mouse works properly.

I believe the same bug is present under Linux as well.

Dell Touchpad, Synaptics driver 15.1.6.2 6/8/10 (up-to-date). 

All other Windows applications scroll properly with the touchpad.
Comment 1 Mikayla Hutchinson [MSFT] 2011-08-23 16:17:59 UTC
Works fine for me in Win7 with a mouse and a Macbook touchpad.

My guess would be that synaptics isn't using standard mouse scroll events but is playing tricks with win32 API. I don't ever see a "standard scrolling mouse cursor", so that must be something added by synaptics.
Comment 2 John Costella 2011-08-23 18:26:55 UTC
I don't agree with Miguel's reclassifying this an "enhancement". MD doesn't work on a laptop unless you plug in an external mouse. That's not a bug?

EVERY other application on Windows AND Ubuntu recognises scrolling with the touchpad, so saying that Synaptics "is playing tricks with win32 API" just doesn't hold water.

Touchpad scrolling on ANY laptop (whether single-finger, down the right side, as has been supported for a decade, or double-finger drag, supported only in the last few years) changes the cursor, to something either resembling a mini vertical scroll bar or (in my case) an up-down arrow with an extra line in between the arrows. (See attached phone photo -- screendumps don't show the mouse cursor.)

I realise that you guys must be shell-shocked after being dumped by Novell, but sticking your heads in the sand and claiming that everyone else (on  multiple operating systems) is doing something tricky and custom is a recipe for pushing a great product (MD) into the dustbin of irrelevance.
Comment 3 John Costella 2011-08-23 18:30:26 UTC
Created attachment 174 [details]
Scroll cursor

Shows the apparently mythical touchpad scroll cursor.
Comment 4 Mikayla Hutchinson [MSFT] 2011-08-23 18:54:59 UTC
I didn't say it's mythical, I simply said it wasn't a standard part of windows. I've seen various cursors implemented by various versions of synaptics.

What I suggested was that Synaptics may have implemented their scrolling by making assumptions about what's under the caret, instead of using normal mouse scroll events like some touchpads use. That could break when the app isn't a normal Win32 app - and MonoDevelop uses the GTK toolkit. Does scrolling work in other GTK apps such as Inkscape or the Gimp?
Comment 5 Jeffrey Stedfast 2011-08-23 19:11:48 UTC
John: this seems relevant: http://blog.alexou.net/2010/07/30/scrolling-in-gtk-apps-with-synaptics-driver/
Comment 6 John Costella 2011-08-23 19:41:51 UTC
OK I've checked GIMP and the same problem happens there, so the problem is indeed with GTK+.

I'm reluctant to fiddle with the registry to kill off that part of the touchpad driver, because (a) it's a low-level, dangerous hack that shouldn't be needed -- I'm running a relatively hack-free machine at the moment for business reasons, (b) it's not clear to me what the corresponding hack would be in Linux, and (c) that page has some reports of success and some of failure.

It would make sense for this to be bumped to GTK+, although I guess that means it may never be fixed. 

Googling, I did find a very similar bug reported a few years ago for Visual Studio  itself, presumably now fixed.

Thanks all. Still contemplating whether Visual Studio may ultimately be the easiest solution.
Comment 7 Jeffrey Stedfast 2011-08-23 19:59:22 UTC
If you are doing Mono for Android development on Windows, Visual Studio is our recommended IDE for now (if that helps).
Comment 8 Mikayla Hutchinson [MSFT] 2011-11-22 15:22:18 UTC
The release notes for GTK 2.24.8  mention synaptics improvements on Windows, maybe this was fixed upstream.
Comment 9 PJ 2013-11-19 17:05:00 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 10 PJ 2013-12-05 18:35:19 UTC
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.

Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.