[Wayland-bugs] [Bug 90613] possibility to disable various timeouts?

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=90613

Peter Hutterer <peter.hutterer at who-t.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
                 CC|                            |peter.hutterer at who-t.net

--- Comment #1 from Peter Hutterer <peter.hutterer at who-t.net> ---
(In reply to Mantas Mikulėnas from comment #0)
> Well, in short, it has many false positives. I think it could at least
> exclude the Tab key, and/or keypresses when a modifier key is being held?
> That would take care of many false-positives with Ctrl/Alt/Super shortcut
> keys.

whoops, tab should definitely be in the list here, and the menu keys too. I'll
get a fix out for that. The "while modifier key is down" gets a bit trickier
because that partially depends on the key layout but it should be doable.

Note that there is a much shorter timeout for single key presses, so if you
just type Ctrl+A you shouldn't be hitting the long timeout. I also have another
patch in the works for Bug 90501 which should probably remove or at least
reduce most of your pain points.

> Anyway, I see the changelog has "the feature is currently enabled for all
> touchpads but will be reduced in the future to only apply to touchpads where
> finger width or pressure data is unreliable". So I'll just wait for that.
> I'm fine with having to add hwdb entries or something.

fwiw, we need thumb detection for that first (Bug 90528)


> — The drag timeout (recently increased to 500 ms). —
> 
> I know it can be cancelled with a tap, and I'm trying to get used to that,
> but it still feels as if the driver is buggy (or lagging like hell).
> 
> I can see the timeout being useful with slow cursor speeds, when one needs
> several swipes to drag something across the screen. But it's something that
> varies greatly between touchpads and AccelSpeed settings. In my case, it's
> mostly useless even with AccelSpeed of 0.0, and outright annoying with 1.0.
> So if the speed is adjustable, I think this timeout should be as well?

At the risk of saying something along the lines of "we know better than you"
but I'm really thinking about getting users to re-train themselves to use the
tap to end the drag. It's a new feature (at least in linux) but I've used it in
OS X for years and it is superior (well, for us driver writers anyway ;) and
becomes second nature quickly.

I don't know that we can change the timeouts around much, that would require
quiet complex and error-prone heuristic (and we don't actually know if the
pointer moves on the screen). Either way, if you want to continue the
discussion on the drag timeout please file a separate bug for that so we don't
mix up the two issues.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-bugs/attachments/20150524/8c032f8d/attachment.html>