On Mon, Mar 18, 2002 at 10:52:17PM +0100, Lars Gullik Bjønnes wrote: > No, they don't have to. Rather they should assume that applications > use XSetSelectionOwner properly and that those applications resends > XSetSelectionOwner with a new timestamp when the selection changes.
Unfortunately this isn't possible: applications cannot get notified when an XSetSelectionOwner() happens from another client. Polling with XConvertSelection is the only way to get the behaviour of Klipper. The xselection.requestor thing doesn't work out btw, and the ICCCM is sadly silent on "our side" of the selection problem. So I don't know the best thing to do... regards john -- I am a complete moron for forgetting about endianness. May I be forever marked as such.
