The X server has always had an issue with time stamps assigned to key presses: they are always relative to when the X server started. This makes it very difficult to compare when a key was pressed to some other event, even on the same PC.
I am curious if there is some mechanism that has crept into X that resolves this situation. I know that network-based games have a problem with this because it is difficult to sequence key strokes generated on different systems.
The closest I have seen it a hack that does a virtual key press in the X system, and syncs time using that. While it is an improvement, it still has the problems of X server and other delays.
I ask on this list because perhaps there is some better way to derive this information using tools provided with openSUSE.
If I could only ask the X server what the base time was it is using for these relative time stamps...
I am wanting this for use in a vehicle that travels up to 120 km/h, and would like to relate key presses to locations. Time is how one does this. I currently have to make due with with the time when my app sees the key press - reading the clock at that time because the X timestamp is rather useless. I would prefer to know when the key press was first sensed by the system. I think the keyboard driver has this info, but X does not propagate it, instead supplying the relative time.
Anyone know what I am talking about?
(Reposted as the earlier got no response. I thought I would try again. Maybe someone else sees it this time.)