Xref:	news-dnh.mv.net comp.os.msdos.djgpp:240
Path:	news-dnh.mv.net!mv!news.sprintlink.net!howland.reston.ans.net!Germany.EU.net!zib-berlin.de!informatik.tu-muenchen.de!paysan
From:	paysan AT informatik DOT tu-muenchen DOT de (Bernd Paysan)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Mouse event timing
Date:	8 Jun 1995 12:26:07 GMT
Organization:	Technische Universitaet Muenchen, Germany
Lines:	16
Distribution:	world
Nntp-Posting-Host:	hphalle4f.informatik.tu-muenchen.de
Originator:	paysan AT hphalle4f DOT informatik DOT tu-muenchen DOT de
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway:	from newsgroup comp.os.msdos.djgpp

I've a small problem with go32's mouse event time stamps: they are computed
using the clock() function of Borland C, which gives the number of ticks
since go32 started (not really - there is a midnight problem, too). For a
reasonable double click detection I have to wait for a timeout after a click
had occured, thus I need to check the time stamp with the actual time. Now
there is no (easy) way to get at the clock() time, but it is easy to read
0040:006C. I fixed this by patching the bcc startup code, so that the
"startup time" is set to midnight. Now only clicks across midnight are not
detected (since the timer switches form 0x1800AF to 0)... but I can live with
it. Can you change the time stamp code form clock() to a read from 0040:006C?

-- 
Bernd Paysan
"Late answers are wrong answers!"
http://www.informatik.tu-muenchen.de/cgi-bin/nph-gateway/hphalle2/~paysan/

- Raw text -