Hmm... I forgot that not grabbing the selection causes the problem that you mention below, namely, that we are no longer notified of further changes to the X Selection.
In that case, your patch won't make much of a difference, as there is already an earlier version of xwinclip that has that precise behavior. It does not make much sense to toggle back and forth between releasing verions that do or do not grab the selection.
There must be some part of the X clipboard mechanism that we just are not understanding.
I picked up two X Window System books today from the ACM book sale on campus today... perhaps one of these will have a better description of the clipboard system than the other books I have.
Harold
Robert Fenk wrote:
On Thursday, November 14, 2002 at 14:19:37, Harold L Hunt II wrote: [...]One side note though... please do not call your xwinclip releases test7, or test8, etc. as this will create a great amount of confusion when trying to determine if a user has a problem with an official release or an independent developer's release. Call them something like xwincip-robf1.tgz.
Well you are right, I just was about to let you know without
knowing your email and thinking too much. I probably will
remove the file from my homepage tomorrow.
Thanks for the patch,Sorry for not providing a patch, but the modified code, I had been reindenting it ... ;/ but you should be able to create a diff with --irgnore-all-space ... Anyway some more notes on the changes: The MS$-Code is from: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winui/WinUI/WindowsUserInterface/DataExchange/Clipboard/UsingtheClipboard.asp To detect selection changes in X11 I used the PropertyNotify event from the RootWindow (XSelectInput in xwinclip.c) if event.xproperty.atom != XA_CUT_BUFFER0 which I just assumed to be right when looking at "xev -id root" ... the problem is that you do not get a SelectionNotify anymore if you do not hold the selection ... Bye Robert
