Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!decwrl!sgi!shinobu!odin!sgi.com!karlton
From: karlton@sgi.com (Phil Karlton)
Newsgroups: comp.windows.x
Subject: Re: Use of X Selections
Message-ID: <1990Dec6.032923.27072@odin.corp.sgi.com>
Date: 6 Dec 90 03:29:23 GMT
References: <LOVE.90Dec1152126@aspen.cs.uiuc.edu>
Sender: news@odin.corp.sgi.com (Net News)
Reply-To: karlton@sgi.com
Distribution: comp
Organization: Silicon Graphics, System Software Division
Lines: 14

In article <LOVE.90Dec1152126@aspen.cs.uiuc.edu>, love@aspen.cs.uiuc.edu (Christopher Love) writes:
|> If my application currently owns a selection (i.e. XA_PRIMARY), and I 
|> subsequently do 
|> 	XSetSelectionOwner(dpy,selection,None);
|> to set the owner to None, should my application expect a SelectionClear 
|> event?  Currently I am not seeing such an event, but ...

Well you should get the event. See the documentation on XSetSelectionOwner.

I do notice that you haven't passed a time stamp in the piece of code
above. If that is really how you've coded it, then you merely have a
bug in your client code.

PK