From xemacs-m  Sun Mar  2 14:44:16 1997
Received: from omega.intranet.com (omega.intranet.com [192.148.106.20])
	by xemacs.org (8.8.5/8.8.5) with SMTP id OAA22381
	for <xemacs-beta@xemacs.org>; Sun, 2 Mar 1997 14:44:14 -0600 (CST)
Received: by omega.intranet.com; (5.65v3.2/1.3/10May95) id AA30962; Sun, 2 Mar 1997 15:44:36 -0500
Date: Sun, 2 Mar 1997 15:43:55 -0500 (EST)
Message-Id: <199703022043.PAA18770@blight.IntraNet.com>
From: Jonathan Edwards <edwards@intranet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Kyle Jones <kyle_jones@wonderworks.com>
Cc: xemacs-beta@xemacs.org
Subject: event-timestamp
In-Reply-To: <QQcfdu08997.199703021733@crystal.WonderWorks.COM>
References: <QQcfdu08997.199703021733@crystal.WonderWorks.COM>
X-Face: #bA9Kpw-a@xMyaNJ-2wie(5Lje^S*i^8!VUOF84U!/jSPG*y@3s4Qu+\-FBQ?vQpE1S1<Vo
 TeWVx=wH}wf_WC]x:D%qd,r*|!~q=gVAWEA;T~3V4};X$r7W!FA(#Zj'E7M^(Tv)

Kyle Jones writes:
> 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.

How about:

last-input-time's value is (13081 . 58940)
  -- a simple built-in variable.

Documentation:
The time (in seconds since Jan 1, 1970) of the last-command-event,
represented as a cons of two 16-bit integers.  This is destructively
modified, so copy it if you want to keep it.

I do wish this recorded milleseconds like current-time does.

