public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Ryan Johnson <ryan.johnson@cs.utoronto.ca> To: cygwin-xfree@cygwin.com Subject: Re: AW: Levovo trackpoint come delayed (reproducable with xev) Date: Tue, 24 Jan 2012 13:52:00 -0000 [thread overview] Message-ID: <4F1EB781.1040304@cs.utoronto.ca> (raw) In-Reply-To: <4F1EAF7D.5030602@dronecode.org.uk> On 24/01/2012 8:17 AM, Jon TURNEY wrote: > On 23/01/2012 21:56, Paul Maier wrote: >>> On 22/01/2012 23:10, Paul Maier wrote: >>>> Lenovo trackpoint scrolling events get buffered somewhere until I release the button: >>>> then I get hundreds of scrolling events all at once. >>>> >>>> I can clearly see these events in xev. >>>> >>>> Result is that I don't really experience scrolling, rather jumping up and down >>>> with a random-like distance. >>>> >>>> With trackpoint I mean that red button in the middle of a Lenovo laptop. >>>> >>>> (Mouse wheel scrolling works perfect, in contrast.) >>> Have you tried the workaround given in [1] ? >>> >>> According to the internet, the trackpoint driver tries to be too clever and >>> doesn't send WM_MOUSEWHEEL messages, but tries to fiddle with the Windows >>> scrollbars directly itself, which obviously isn't going to work well for an X >>> window :S >>> >>> [1] http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-trackpoint >> I can't find any of the files tp4*.dat on my PC (I'm running Windows 7) - see console output below. > It seems that FAQ might need a little updating, that file might found under > %PROGRAMFILES% now, C:\Program Files\Synaptics\SynTP\TP4table.dat or > C:\Program Files\Lenovo\Trackpoint\tp4table.dat for example. I've done this with mintty on my machine as follows: > --- TP4scrol-orig.dat 2011-12-11 16:33:22.742741700 -0500 > +++ TP4scrol.dat 2011-12-30 00:59:46.793965200 -0500 > @@ -24,6 +24,9 @@ > ; Pass 0 rules (These rules run first) > ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; > > +; mintty > +*,*,mintty.exe,*,*,*,WheelStd,0,9 > + > ; Windows IE3 patch for 2 button systems > *,*,iexplore.exe,*,Shell DocObject View,HTML_Internet > Explorer,Standard,0,5 I assume the line for X apps would be the similar. Note that you have to put the same line in TP4table.dat, then kill and restart all the TP* processes. One of them (sorry, can't remember which) is the "parent" process and will start the others if it sees they're missing. Good luck! Ryan -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
next prev parent reply other threads:[~2012-01-24 13:52 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-22 23:11 Paul Maier 2012-01-23 13:18 ` Jon TURNEY 2012-01-23 21:57 ` AW: " Paul Maier 2012-01-24 13:17 ` Jon TURNEY 2012-01-24 13:52 ` Ryan Johnson [this message] [not found] ` <000001ccde8a$f0fc2010$d2f46030$@de> [not found] ` <4F2A7C93.6080705@dronecode.org.uk> 2012-02-02 19:47 ` AW: QAW: " Paul Maier 2012-02-03 15:49 ` Jon TURNEY 2012-02-03 22:39 ` AW: " Paul Maier 2012-07-22 0:42 ` Levovo trackpoint events " Paul Maier 2012-08-06 13:31 ` Jon TURNEY [not found] ` <000001cd7a5c$88a929e0$99fb7da0$@de> 2012-08-15 17:52 ` AW: " Jon TURNEY 2012-02-02 20:33 ` AW: QAW: AW: Levovo trackpoint " Paul Maier
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=4F1EB781.1040304@cs.utoronto.ca \ --to=ryan.johnson@cs.utoronto.ca \ --cc=cygwin-xfree@cygwin.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).