On Wednesday, June 5, 2019 at 9:23:26 PM UTC+8, Alex Harsanyi wrote: > > > > On Wednesday, June 5, 2019 at 8:51:48 PM UTC+8, evdubs wrote: >> >> I ran the program with your modifications, but counter to the >> documentation >> <https://docs.racket-lang.org/gui/event_.html?q=get-time-stamp#%28meth._%28%28%28lib._mred%2Fmain..rkt%29._event~25%29._get-time-stamp%29%29>, >> >> the values I get from get-time-stamp don't seem at all similar to >> current-milliseconds or current-inexact-milliseconds. I ended up >> defining delta as follows (with 1559695139340 being a guess): >> >> (define delta (- (current-inexact-milliseconds) 1559695139340 (send event >> get-time-stamp))) >> >> > On my machine, `get-time-stamp` always returns 0 -- this indicates that > the event% object itself is copied somewhere along the way but the > timestamp is not copied, The 1559695139340 is just the unix timestamp from > when you ran the code first time. I don't think the mouse test is relevant > as is... unfortunately I don't have any more suggestions for now... >
It looks like the `get-time-stamp` returns a value that is not what the documentation specifies and it is also platform specific, I created an issue with the relevant details here: https://github.com/racket/gui/issues/132 For now, I cannot think of a way to determine how old a mouse event is when the callback is invoked. > > Alex. > > -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/10aa0c2f-b5f5-48ff-8f0a-66ce99fbd2b0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
