[Vm-dev] [OpenSmalltalk/opensmalltalk-vm] Win32 event generation mixes up timeGetTime() and GetMessageTime() (#509)

[Christoph Thiede]

Just thinking aloud:

At the moment, there are three different time sources used in the win32 implementation:

- `Time self millisecondClockValue` based on `#utcMicrosecondClock` which counts since from 1901.
- `Time eventMillisecondClock` based on `ioMSecs()` which counts since system start. (used for DnD events)
- `MSG>>time` (used for most events)
- `GetMessageTime()` (used for mouse events, too, but only for checking time deltas)

I just validated my assumption that `GetMessageTime()` returns values similar to `MSG>>time`, deviation could only result from a long event processing time on the VM side. As regular events are not recorded by the VM during DnD, this problem does not seem to be relevant, so I will patch `recordDragDropEvent()` to use `GetMessageTime()` now, too. 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/509#issuecomment-685801137
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20200902/01d1c396/attachment.html>