public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: "Paul Maier" <svn-user@web.de>
To: <cygwin-xfree@cygwin.com>
Cc: <dickey@his.com>
Subject: AW: scrolling xterm with Levovo trackpoint
Date: Mon, 19 Dec 2011 19:47:00 -0000	[thread overview]
Message-ID: <005101ccbcb3$d29d16e0$77d744a0$@de> (raw)
In-Reply-To: <20111216012357.GA7076@debian50-32.invisible-island.net>

> > when I reboot my PC, scrolling an xterm with a Levovo trackpoint works (mostly) fine, very smooth
> and good speed.
> > Then I work for a while and some condition, that I couldn't find out yet, corrupts it.
> > It then doesn't scroll WHILE you hold that Trackpoint middle button down, but after you RELEASED it;
> > on release it catches up for all the scrolling that should have appeared before.
> > It's then not really scrolling but guesswork, how much of pressure might be the right, then you
> release
> > and you see where you got scrolled by that.
> >
> > Does anybody have the same experience or an idea what could be the cause of that switching from
> working to not working?
> 
> not exactly - if it's using wheel mouse (buttons 4/5) those should be
> sent continuously.  xterm isn't necessarily going to keep up with
> a continuous stream of events, so there could be a buildup of events
> making xterm not seem to do much for a while.  I made some improvements
> to filter out duplicate window movement/resizing, but that shouldn't be
> related.

Hi Thomas!

thank you for your response.

I experience a difference between the Trackpoint and the mouse wheel:
the mouse wheel always works fine.

Even an xterm that lived for quite a while and that shows this deferred scrolling
on using the trackpoint, I can without problem scroll using the wheel or using xterm's scrollbar.

I think we agree, that the trackpoint events ARE generated (because otherwise there would not
be deferred scrolling but no scrolling).

So the question is, where these events get buffered. 
If xterm treats wheel and trackpoint the same, the trackpoint events get buffered in a component
between XWin and xterm?

In case you want me to run a beta test, also for the blind key (dead key) issue,
pls let me know.

Regards,
  Paul



--
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/


      reply	other threads:[~2011-12-17 12:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-10 12:24 Paul Maier
2011-12-16  9:14 ` Thomas Dickey
2011-12-19 19:47   ` Paul Maier [this message]

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='005101ccbcb3$d29d16e0$77d744a0$@de' \
    --to=svn-user@web.de \
    --cc=cygwin-xfree@cygwin.com \
    --cc=dickey@his.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: link
Be 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).