https://bugs.kde.org/show_bug.cgi?id=478824
Bug ID: 478824
Summary: Feature Request: delay user input on new ui elements
(like popups or new windows)
Classification: Plasma
Product: plasmashell
Version: master
Platform: Other
OS: All
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: github5...@der-he.de
CC: k...@davidedmundson.co.uk
Target Milestone: 1.0
I do not know which product/component to report this on, as this is a request
to KDE/plasma in general, so I tried to guess the most generic one.
**problem definition**
Within every modern system it's quite common that new ui elements (like every
kind of popups, new windows, etc.) instantaneously recognize user input,
despite the fact that a normal human user cannot react on that new ui element
with intent within the first 100-500 ms (I'd even say within the first
second...).
I'm pretty sure everyone already had some happening in the past where he wanted
to click on some ui element and some other ui element (maybe even a completely
different user application) pops up right under the mouse pointer some
microseconds before the click happens and the wrong ui element gets the "click"
event. Unintentionally. Because no one is able to react within microseconds (or
even a bunch of milliseconds or even a whole second).
**proposed solution**
I'd like to have a central configure option which "delays" any user input to
new ui elements for some sane amount of time after its creation. With a sane
default of maybe some hundreds of milliseconds - where this kind of "sane"
default is indeed open for discussion.
**additional question**
I don't know if this can be implemented in the compositor or some other
component or even some toolkit below or even if I'm completely wrong here. I
just want to point on this topic. So, please:
As this is a quite common problem probably every fairly experienced user
already suffered from but it's still not implemented by any system or ui
toolkit (at least not that I know of, no gtk/gnome, no kde/qt, no MS Windows,
no macOS/iOS... not even a single one) I'm asking myself what's the reason
against implementing some countermeasure?
If there are good reasons for having user input instantaneously available to
some freshly created element, there could be some option for the author(dev) to
manually override such a system default or even some project/compiler option
for some build default. Maybe even some gui type elements are preferred to be
on the one or other side. But I'm sill wondering why there seems to be
currently no single solution in any of the modern systems. I simply do not
understand this.
Real world example: Quite recently I wanted to unlock my phone to look for
something. The Moment I tried to unlock the phone there was an incoming call
and instead of unlocking the phone I unintentionally canceled the incoming
call. Does my mobile phone really thinks anyone wants to decline an incoming
phone call roughly 1 millisecond after it asked for? With intent? I don't think
so...
--
You are receiving this mail because:
You are watching all bug changes.
