Opened 3 years ago

Last modified 2 months ago

#12837 new enhancement

mouse deadzone

Reported by: AlienSoldier Owned by: stippi
Priority: critical Milestone: Unscheduled
Component: User Interface Version: R1/Development
Keywords: mouse Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

When using a mix of mouse acceleration and 1080 resolution, it come a point where just vibration on a table can cause the computer to exit a screen saver, pop the media button interface in video played in media player and thing like that. It is also one of the most anoying thing ever to empty the trash as half the time the second button give you the good option and the other half it ask you if you want to create a new link for the trash because i moved a few pixel while pressing the button. Having some kind of mouse deadzone proportional to the DPI/resolution would really improve the usability. I rate it as critical because it highly increase my daily swearing over sane level :)

Change History (7)

comment:1 by nephele, 2 months ago

I would like to add that this would be highly desireable for (wacom) tablets too, especially for double clicking, trying to double click requires an insane ammount of precision :)

comment:2 by pulkomandy, 2 months ago

There is already a "deadzone" to detect a drag and drop versus double click, but that one is indeed a bit small (even on my non-hidpi system I can easily do accidental drag and drop).

And it doesn't cover the other cases.

At what level should this be implemented? input_server? Specifically in the few annoying cases (screen saver, media player, and drag qnd drop detection)?

comment:3 by AlienSoldier, 2 months ago

i guess it could be made default but to be possible to overwrite by an app (like a free hand drawing tool or a video game as i don't lag either).

comment:4 by nephele, 2 months ago

I wouldn't want to loose precision on i.e a tablet, so the right layer is an interesting question, I suppose it might make sense wherever the double click detection is for instance.

comment:5 by X512, 2 months ago

I don't think that implementing dead zone individually is a problem. Implementation is trivial. Dead zone radius can be made available from API and editable from settings program. Also for screensaver/full screen media player dead zone can not work properly. Pointer moves caused by vibration during long time can enter outside dead zone. Some velocity based method is required.

comment:6 by pulkomandy, 2 months ago

The dead zone is of course linked to a delay/velocity, otherwise you could never move the mouse.

comment:7 by stippi, 2 months ago

Yes, the layer where to put this is interesting. I think the Screensaver and MediaPlayer should indeed actively avoid reacting to tiny movements.... because in a drawing app, you want these tiny movements to register. So a "deadzone" feature cannot be placed in the driver. (Although the Wacom driver actively tries to prevent jitter by applying a filter.) But the driver should allow a small distance between clicks in order to still register as double or tripple clicks. (The driver just increases a "click count", there is no concept of "double click" at the input device add-on level.)

Note: See TracTickets for help on using tickets.