Tap recognition
Brought to you by:
pete-woods,
tawsi
Menu
▾
▴
Logged In: YES
user_id=1304170
Tell us _exactly_ how you are tapping.
We need to be able to replicate what you're seeing.
Logged In: YES
user_id=153018
I can confirm that many taps on the trackpad are missed on my
machine. I can also say that it can occur without heavy processor
activity. Often, many taps are missed in sequence; after I
"insist" (repeated taps), all taps are caught for a while. No obvious
onset, though using a hot corner for right-click seems to sometimes
trigger the issue.
My settings are simple (BR corner for right-click; vertical scroll region at
right; no 2-finger anything; do not ignore "accidental input"; no
dragging...) on a PB 12" 2004.
(Another small issue: Sometimes, if I scroll up from my right-click hot
corner, the right-click gets triggered even if my finger never left the
trackpad while going up.)
Otherwise, keep up the great work.
Logged In: YES
user_id=1304170
We really do need to be able to replicate your bugs if we are to fix them.
I have managed to get my bottom right hotspot to trigger without lifting
my finger off once like you said, so I will look into that.
However I cannot find the pad ever missing any of my taps. You may
want to try increasing the tap tolerance in the advanced tab. If your
finger slides at all when tapping this will help. It will also help if you have
large fingers.
If you could really say exactly what you are doing when these missed
taps occur it would help us get an idea of actually what is going on.
Logged In: YES
user_id=153018
Sorry, but tap interactions cannot be screen captured without a vidcam!
I am trying to be precise.
I mostly test by tap-switching between a few active windows in the
terminal, alternating with pad scrolls and corner-based right-taps. I then
usually tap out of the contextual menu. I will often find that a few taps
will fail to bring another window to the front. Tapping in the scroll region
does not seem to help, but there are taps missed in the center of the
pad. Soft taps seem missed more often. (But there, I should deinstall
and compare to be sure...)
I doubled the Tap tolerence, but still experience the problem; though just
possibly less. (My fingers are actually small, for the record.)
I am quite certain I have even seen cases where even the button click
was lost, but that is hard for me to confirm, and more rare if real...
Logged In: YES
user_id=1304170
I'm sorry, but I've just spent 10 minutes with your exact configuration
tapping around half a dozen terminals trying to get it to not detect any of
my taps without any luck at all.
When you have the context-menu up over one window, tapping once
over another window should not bring it up. For some reason Apple
seems to have chosen that the window stays grey but is kinda selected
too. I don't really understand it, but exactly the same thing occurs when
you use a real mouse (as I have just confirmed).
If physical clicks are being lost then I really don't understand what could
be going on. I'll have to talk to tawsi about it.
Logged In: YES
user_id=153018
So I guess our machine's behaviour differs, which will make identifying the
bug more fun. I think I am aware of the contextual menu behaviour you
point out; in my understanding, if the context menu is up, the first tap
should just dismiss it (sometimes it fails to) and, after it is gone,
subsequent taps should raise the next window (also sometimes fails.)
I am beginning to think that, sometimes, I just tap too softly...
Logged In: YES
user_id=153018
So I guess our machine's behaviour differs, which will make identifying the
bug more fun. I think I am aware of the contextual menu behaviour you
point out; in my understanding, if the context menu is up, the first tap
should just dismiss it (sometimes it fails to) and, after it is gone,
subsequent taps should raise the next window (also sometimes fails.)
I am beginning to think that, sometimes, I just tap too softly...
Logged In: NO
I increased the tab tolerance from 10 to 20 and now it seems to work far
better, though the problem still remains. Both tab recognition and
activation of the linear scroll region work better now. (meaning I don't
need to scroll one or two trackpad length before the driver interprets my
movement as a linear scroll input).
I tried to figure out what I'm doing before the driver loses one tab ... and
I failed. There is no specific action causing the missed tab. It happens
in every application I'm using and under many circumstances (all long
line of tabs, the first tab, the second tab.) The only thing I can definitely
approve is that the "missed second tab" happens more often.
It also seems that increasing the width of the linear scrolling area (T/R)
helps avoiding the unitentional tab recognition when scrolling in in the
linear scrolling area.