Summary: | Mouse input single / double click should be changed to: safe action, quick confirm, and long confirm | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | Aaron Peterson <alpeterson> |
Component: | kcm_mouse | Assignee: | Marie Loise Nolden <nolden> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | wishlist | CC: | groszdanielpub, nate |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Unspecified | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Aaron Peterson
2009-05-25 07:51:45 UTC
*** Bug 193982 has been marked as a duplicate of this bug. *** As far as I know on Windows double clicks are used not as a confirmation but where single click has an other action (such as selecting the icon). Where there is no such action, it uses single click (e. g. for web links where opening something from a web page or sending a form is comparable to opening a file from the file manager). As when Windows uses double click the single click action is practically never needed, I think the current KDE defaults of using single click everywhere are right. >As far as I know on Windows double clicks are used not as a confirmation but
where single click has an other action (such as selecting the icon). Where
I think there is room for us to both be correct, It serves as a sanity check, and it allows single click to do other things.
I believe I have another bug open requesting double click on icons as default, and I think that is a political battle that I can't win directly.
This generalization is more intended as a way to extend into new input devices.
For example, with touch screens... a slide to unlock is an example of a sanity check...
I'm thinking of people with ALS, or spinal damage.
Alternate actions performed by gesture, will need to be categorized by how dangerous they are.
That is the main point I am making, and it would be cool if QT supported that.. (I think that KDE will only do it if QT does it.. and QT is moving back into mobile.. this time with touch screens)
This would sure help with the transition to touch screen computing, where we have sliders and other gizmos to make sure we are not a cat before doing unsafe options. Perhaps this is an upstream thing for QT? This isn't something that's really possible to do at the window manager level. It would have to be done in each individual app to avoid stomping on apps' expected actions and breaking some of them. |