[kwin] [Bug 393663] mouse events and menus should be triggered on mouse-up to give user a chance to cancel

2018-05-08 Thread myusualnickname
https://bugs.kde.org/show_bug.cgi?id=393663

--- Comment #5 from myusualnickn...@gmail.com  ---
(In reply to Christoph Feck from comment #4)
> *** Bug 393695 has been marked as a duplicate of this bug. ***

Thank you!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 393663] mouse events and menus should be triggered on mouse-up to give user a chance to cancel

2018-04-30 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=393663

Christoph Feck  changed:

   What|Removed |Added

 CC||ideomot...@protonmail.com

--- Comment #4 from Christoph Feck  ---
*** Bug 393695 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 393663] mouse events and menus should be triggered on mouse-up to give user a chance to cancel

2018-04-30 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=393663

--- Comment #3 from Christoph Feck  ---
Needs to be fixed in Qt, see https://bugreports.qt.io/browse/QTBUG-57849

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 393663] mouse events and menus should be triggered on mouse-up to give user a chance to cancel

2018-04-29 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=393663

Martin Flöser  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Martin Flöser  ---
I'm sorry but this is outside the scope and possibilities of a window manager.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 393663] mouse events and menus should be triggered on mouse-up to give user a chance to cancel

2018-04-29 Thread myusualnickname
https://bugs.kde.org/show_bug.cgi?id=393663

--- Comment #1 from myusualnickn...@gmail.com  ---
about 2 out of 5 times people who click while the mouse is moving didn't mean
to do the click.   

For users with mobility problems, it is extra important to make sure that they
actually mean to do the click.. so they may struggle a bit to actually trigger
the event, but doing the false event is much worse...  better to make them give
confirmed good input than start opening a program that will take 10 minutes to
load...   Also note, the people with mobility problems also often don't have
enough money to buy a good computer.

-- 
You are receiving this mail because:
You are watching all bug changes.