Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!lll-winken!arisia!sgi!shinobu!odin!sgi.com!karlton From: karlton@sgi.com (Phil Karlton) Newsgroups: comp.windows.x Subject: Re: CUTBUFFERS too small Message-ID: <1436@odin.SGI.COM> Date: 14 Nov 89 21:32:01 GMT References: <8911091726.AA03986@devnull.sun.com> Sender: news@odin.SGI.COM Reply-To: karlton@sgi.com (Phil Karlton) Organization: Silicon Graphics, WorkGroup Products Division Lines: 42 In article , wjh+@ANDREW.CMU.EDU (Fred Hansen) writes: > What exactly is the recommended ICCCM scheme? In particular, > what is the relationship of CLIPBOARD and PRIMARY? The notions of the CLIPBOARD and PRIMARY selections are independent. The CLIPBOARD is intended to be used for those objects that have been deleted (or copied to a trash bin, etc.). The PRIMARY selection is for those objects that have been merely selected, but no information deleting action has taken place. The client that wants the latest cut value should get that from the CLIPBOARD. A "paste" operation is a typical reason to do this. Other than when a clipboard client is being used, usally there is no representation on the screen of the object that is referenced by the CLIPBOARD. The client that wants to get the current value of an object (or some attribute of the current object) would get that from the PRIMARY selection. A "copy" operation is a typical reason to do this. Almost invariably there will be some highlighting on the screen of the object that is referenced by PRIMARY > Should a > client that takes ownership of PRIMARY also take ownership > of CLIPBOARD? Only at the point that the user executes some sort of "delete" or "cut" operation. > Should a client that wants the latest cut value > check the TIMESTAMP value from each of PRIMARY and > CLIPBOARD? No. The latest "cut value" should always be in CLIPBOARD. PK -- Phil Karlton karlton@sgi.com Silicon Graphics Computer Systems 415-335-1557 2011 N. Shoreline Blvd. Mountain View, CA 94039