9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: andrey mirtchovski <mirtchovski@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] evoluent mouse review
Date: Wed,  6 Jan 2010 00:05:25 -0700	[thread overview]
Message-ID: <14ec7b181001052305x52fd6985n5754974534e02186@mail.gmail.com> (raw)
In-Reply-To: <6e35c0621001052152s2d71c3b3vf00b7d3320003782@mail.gmail.com>

here's a report. i obviously don't know enough about touch controls to
be of any use, but i'd like to help with testing.

- on my snow leopard macbook pro it appears that the multitouch
library is found and devdraw is compiled with -DMULTITOUCH (indeed if
i undef this the problem goes away).

- multitouch works according to osx and the touchCallback routine is
called with the correct number of nFingers (at least for n<=5),
unfortunately at no point does the classifyTouch classify any touches
as button clicks.

- there are two preferences for the trackpad -- 'tap to click'
(available for primary button with one-finger tap and secondary button
with two-finger tap, there is not tertiary button option) or 'press to
click' (which generates a primary button click only, regardless of how
many buttons were pressed when the clicking occurred). here the
behaviour differs a bit in terms of expected actions, although the end
result is the same:

- pressing to click with one finger generates a correct primary mouse
button event (even secondary, if the right side of the trackpad is
set) for mouseevent, however with osx.touched set by touchCallback we
try searching the higher-order bits of "but" and find nothing

- tapping to click generates a correct primary or secondary mouse
button event, but again gets caught by osx.touched set and nothing in
the upper bits in mouseevent()

in both cases the keystroke event is generated by osx itself and not
by touchCallback.

if i print out the number of fingers passes to touchCallback and the
resulting buttons as calculated by classifyTouch, i see the correct
value of nFingers but always zero buttons pressed. i was expecting (in
order for chording to work) that if i tap a finger i would see a
button stroke, instead i see multiple calls to touchCallback but no
button classification.

digging a bit deeper, it appears that the size of my click is around
0.2 to 0.5 (with a size sensitivity of 1.25) so my threshold time
never accumulates. pressing and holding a full finger onto the
trackpad finally lets the threshold time accumulate, but that's now
too long for a click to be generated. setting the size sensitivity to
some low value (0.05) finally lets classifyTouch report appropriate
clicks if i tap in the upper part of the trackpad but those do not
translate into actual click events sent to acme. the upper part of the
trackpad is exactly the wrong place for one to be clicking on a
macbook though...

unfortunately, i think a proper solution for trackpads may be a bit
more involved than what my simple understanding of the problem can
fix.

ps: two-finger scrolling works as usual, but that's outside of the
realm of multitouch (i.e., it's worked since leopard)



  reply	other threads:[~2010-01-06  7:05 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-24 16:13 Russ Cox
2008-06-24 20:32 ` Dave Eckhardt
2008-06-24 20:46   ` andrey mirtchovski
2008-06-26  7:45     ` Nick LaForge
2008-06-26 17:22       ` Dave Eckhardt
2008-06-26 17:37         ` erik quanstrom
2010-01-03 21:52 ` Mathieu Lonjaret
2010-01-04  4:41   ` Russ Cox
2010-01-04 16:12     ` David Leimbach
2010-01-04 17:14       ` Benjamin Huntsman
2010-01-04 18:14         ` Anthony Sorace
2010-01-04 18:26           ` David Leimbach
2010-01-06  5:03     ` Russ Cox
2010-01-06  5:20       ` andrey mirtchovski
2010-01-06  5:52         ` Jack Johnson
2010-01-06  7:05           ` andrey mirtchovski [this message]
2010-01-06 13:59       ` David Leimbach
2010-01-06 14:58         ` hiro
2010-01-07  0:44         ` blstuart
2012-02-21 15:03       ` Quico Moya
2012-02-21 15:28         ` Jeff Sickel
2012-02-21 15:52         ` Russ Cox
2012-02-22 17:19     ` Quico Moya

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=14ec7b181001052305x52fd6985n5754974534e02186@mail.gmail.com \
    --to=mirtchovski@gmail.com \
    --cc=9fans@9fans.net \
    /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 NNTP newsgroup(s).