Closed
Bug 269124
Opened 20 years ago
Closed 20 years ago
Use GetInputState rather than GetQueueStatus(QS_INPUT)
Categories
(Core :: XUL, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: bryner, Assigned: bryner)
Details
(Keywords: perf)
Attachments
(1 file)
|
1.02 KB,
patch
|
Details | Diff | Splinter Review |
We use GetQueueStatus(QS_INPUT) in nsWindow::GetLastInputEventTime() to determine if there are new input messages waiting to be processed. GetInputState() has the same effect but is quite a bit faster (we call this a ton during parsing). References: http://msdn.microsoft.com/library/en-us/winui/winui/windowsuserinterface/windowing/messagesandmessagequeues/messagesandmessagequeuesreference/messagesandmessagequeuesfunctions/getqueuestatus.asp http://msdn.microsoft.com/library/en-us/winui/winui/windowsuserinterface/windowing/messagesandmessagequeues/messagesandmessagequeuesreference/messagesandmessagequeuesfunctions/getinputstate.asp
| Assignee | ||
Comment 1•20 years ago
|
||
| Assignee | ||
Updated•20 years ago
|
Attachment #165533 -
Flags: superreview?(roc)
Attachment #165533 -
Flags: review?(emaijala)
| Assignee | ||
Comment 2•20 years ago
|
||
Comment on attachment 165533 [details] [diff] [review] patch Oops... this doesn't look at mouse moves, which are a significant part of user-input events.
Attachment #165533 -
Flags: superreview?(roc)
Attachment #165533 -
Flags: review?(emaijala)
| Assignee | ||
Comment 3•20 years ago
|
||
resolving invalid... sorry for the spam.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•