|
From: Daniel J S. <dan...@ie...> - 2006-07-18 18:05:46
|
Timoth=E9e Lecomte wrote: > Dave Denholm wrote: >=20 >> Ah - tell you what - there is one thing that is timing dependent. >> >> When you acquire a selection, you're supposed to give a >> timestamp. That is a server time, and it usually comes from the X >> event that triggered the action to acquire the selection. But gnuplot >> doesn't have such an event. IIRC, we use "currenttime" for that, but >> that isn't a real time. >> =20 >=20 > Hmm. I wrote the code just a few months ago to provide this timestamp. = I=20 > took the time as plot->time. I realise now that this time is only=20 > updated at a button release event, and put to 0 at each "record", so if= =20 > the user doesn't click on the window this timestamp may have a useless=20 > value. Could have been a problem. But I eventually whittled things down to the = one problem Dave is keen to. I did notice that the client used to call a= XA_TIMESTAMP selector request. But now it no longer does. Perhaps that= was an issue (that X could resolve with the XA_TIMESTAMP property reques= t), and now has gone away. Dan |