Closed Bug 484468 Opened 17 years ago Closed 15 years ago

GetMessageTime() needs to be implemented

Categories

(Core :: Widget: Win32, defect)

All
Windows CE
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: dougt, Unassigned)

References

()

Details

Attachments

(1 file, 1 obsolete file)

Currently GetMessageTime just returns zero on windows mobile. This value is important for mouse events (it is set as the time attribute).
Attached patch gettimecount simulation (obsolete) — — Splinter Review
good enough simulation of GetMessageTime for the usage in nsWindow.cpp.
Attachment #368596 - Flags: review?(bugmail)
Attachment #368596 - Flags: review?(bugmail) → review-
Attachment #368596 - Attachment is obsolete: true
Attachment #368597 - Flags: review?(bugmail)
Comment on attachment 368597 [details] [diff] [review] gettimecount simulation This isn't quite the behavior that is expected from GetMessageTime(). It seems we could get the actual time of the message from MSG.time. Could you look at doing that?
Attachment #368597 - Flags: review?(bugmail) → review-
that is why i called it a simulation. the alternative, as I mentioned in IRC, is to overload PeekMessage and GetMessage (using the shunt), record the time, then return that. However, since GetMessageTime is only used in this file, and it is only used to set the right time on the mouseevents that we are creating (which we create when we get the WM_ event), I proposed that we just simulate the time.
we might be able to just above GetMessageTime() all together and use something that gives us access to the event. looking....
GetMessage and PeekMessage are called in a few different places. We could plumb the MSG pointer from the Get/Peek Message callsite to where GetMessageTime() is called. Or we can overload both APIs in our shunt and remember the message time. I am not convinced that it matters really since the event time will just be uniformly increased. And this is much better than what we have. I am open to other suggestions.
vlad, do you have an opinion here?
We have the time in nsAppShell::ProcessNextNativeEvent because we have the MSG there, right? So just stick the time in a global (or a static element on nsAppShell), and access it from nsWindow. Could just get rid of GetMessageTime calls altogether and use that approach cross-platform.
Assignee: doug.turner → nobody
Component: Geolocation → Widget: Win32
QA Contact: geolocation → win32
Worked around this in bug 507064.
Doug, can we close this out?
why would we not just want to fix this and remove the workaround that dolske added?
WinCE/Windows Mobile support has been removed from the main build system, Spidermonkey, mobile installer, in-app updater and so on (see bug 614720, bug 554087 and all their dependants). Until such point where MS decide to release a Windows Phone 7 NDK and the decision is made to port to that platform, this is WONTFIX. Filter bugmail on WinCEMassWONTFIX.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: