Peter Kümmel wrote:
Peter Kümmel wrote:
Dov Feldstern wrote:
Peter Kümmel wrote:
Dov Feldstern wrote:
Peter Kümmel wrote:
Dov Feldstern wrote:
Again, to reproduce, just hold down any of the arrow keys, and keep
holding it down. At some point it will just stop moving --- I assume
this will happen on any machine if you hold the key long enough. From
then on, anytime you hold down the key, only the single initial keypress
event will be processed.
I assume QCoreApplication::hasPendingEvents() is always true.
The Qt doc says:
"void QEvent::accept ()
Sets the accept flag of the event object, the equivalent of callign
setAccepted(true).
Setting the accept parameter indicates that the event receiver wants
the event.
Unwanted events might be propagated to the parent widget."
(a spelling error in the Qt docs...)
So does attached patch help?
No :(, if anything it's worse: now holding a key is *always* processed
as only a single keypress, there's not even an initial period when the
cursor zooms along...
Seems we could not use QCoreApplication::hasPendingEvents() to check if
the system is busy.
Seems I have to look for my 233MHz notebook. ;)
Peter
The truth is, I don't know that this is directly related to the machine
on which it's running. My machine is quite powerful --- it's a Pentium
IV 3.0 GHz; and I don't see any jump in the system load when I start
scrolling, either: not when I start and the cursor is still zooming
along, nor when it suddenly becomes saturated with events and stops
moving...
