Closed Bug 489288 Opened 15 years ago Closed 15 years ago

Wince WaitMessage is wrong

Categories

(Core :: Widget: Win32, defect)

x86
Windows CE
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: dougt, Assigned: dougt)

References

()

Details

Attachments

(1 file)

in the simulation of WaitMessage(), we should use QS_POSTMESSAGE instead of QS_ALLEVENTS.

According to the documentation [1], WaitMessage returns control to the calling thread when "a new message is placed in the thread's message queue".  This is consistent with the QS_POSTMESSAGE parameter [2].

[1] http://msdn.microsoft.com/en-us/library/ms644956%28VS.85%29.aspx  (w32)
[2] http://msdn.microsoft.com/en-us/library/ms961244.aspx  (wince)


Right now, what we have is going to be return more often than needed.
Attached patch patch v.1Splinter Review
Assignee: nobody → doug.turner
Attachment #373798 - Flags: review?
Hrm, are you sure about this?  QS_POSTMESSAGE is basically going to ignore most input, paint etc. messages, which I'm pretty sure WaitMessage() won't.
yeah, weird huh.  we tried this patch, and it is terrible;  dropping event.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
Attachment #373798 - Flags: review? → review-
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: