From xemacs-m  Sun Mar  2 11:33:33 1997
Received: from crystal.WonderWorks.COM (crystal.WonderWorks.com [192.203.206.1])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id LAA27929
	for <xemacs-beta@xemacs.org>; Sun, 2 Mar 1997 11:33:28 -0600 (CST)
Received: by crystal.WonderWorks.COM 
	id QQcfdu08997; Sun, 2 Mar 1997 12:33:27 -0500 (EST)
Date: Sun, 2 Mar 1997 12:33:27 -0500 (EST)
Message-Id: <QQcfdu08997.199703021733@crystal.WonderWorks.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Kyle Jones <kyle_jones@wonderworks.com>
To: xemacs-beta@xemacs.org
Subject: event-timestamp
X-Face: /cA45WHG7jWq>(O3&Z57Y<"WsX5ddc,4c#w0F*zrV#=M
        0@~@,s;b,aMtR5Sqs"+nU.z^CSFQ9t`z2>W,S,]:[+2^
        Nbf6v4g>!&,7R4Ot4Wg{&tm=WX7P["9%a)_da48-^tGy
        ,qz]Z,Zz\{E.,]'EO+F)@$KtF&V

Today I wsa trying to answer the question, "How I figure out how
long XEmacs has been idle?"  The answer should be to take the
event time of the last command event and subtract it from the
current time.  This requires that event-timestamp return a value
relative to some fixed (and known!) point in time.

But it doesn't.  All I can tell is that the value seems to be
kept in milliseconds.  If it is relative to some fixed point in
time, I have no idea when that is.  If it is relative to the
epoch, then that number is too large to be kept in a 32-bit int
and is being truncated.

event-timestamp would be more useful if it returned a list in the
same form as current-time.  The time returned would be the time
XEmacs processed the event, rather than the X11 event timestamp
or whatever XEmacs is currently returning.

If event-timestamp is being used elsewhere I would cheerfully
accept another function (event-time, event-time-list, event-frog,
whatever) that behaved in the way I want.

