Article View: gnu.epoch.misc
Article #1373Selection ownership and requests in epoch
From: Warner Losh
Date: Fri, 22 May 1992 17:44
Date: Fri, 22 May 1992 17:44
21 lines
1263 bytes
1263 bytes
In selection.c we find: XConvertSelection(dpy,select,typ,prop,win,CurrentTime); In the ICCCM we find the following "Clients should not use CurrentTime for the time field of ConvertSelection requests. They should use the timestamp of the event that caused the request to be made." My question is, why does epoch use CurrentTime here? Shouldn't it use the timestamp of either the keystroke or the click that caused the selection request to be made? Alternatively, shouldn't it use the timestamp of the last event that was processed? Granted, Xt handles this case correctly, but other toolkits do not (OI is one example). Warner -- Warner Losh imp@Solbourne.COM "Something grabbed a hold of my hand/ I didn't know it had my hand/ but that's when all my troubles began" TMBG
Technical Details
Message-ID:
<BonyM3.Gvw@solbourne.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!stan!impShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fc7ee,6fec05c91df8828f,start X-Google-Attributes: gidfc7ee,public X-Google-ArrivalTime: 1992-05-22 06:19:18 PST Newsgroups: gnu.epoch.misc Path: arc1-ca.pugleaf.net!sparky!uunet!stan!imp From: imp@solbourne.com (Warner Losh) Subject: Selection ownership and requests in epoch Message-ID: <BonyM3.Gvw@solbourne.com> Organization: Solbourne, User Interface Group Date: Fri, 22 May 1992 17:44:27 GMT Lines: 21