John Levon <[EMAIL PROTECTED]> writes:
>> btw. from where and how is the XSetSelectionOwner done? IMHO Klipper
>> should only ask once unless the timestamp changes.... I wonder:
>
| It /only/ gets called when we finish a selection ie button 1 release.
yes, I saw that.
| IMO Klipper's behaviour is pretty broken, and looks nothing like the X
| selection model, old OR new.
>
>> (btw. yes as a variable name is just horrible !yes == no o' the joy)
>
| hmm yeah
>
>> Is the problem really that we call haveSelection way to often? On
>> every cursor blink perhaps?
>
| I'm not that lame !
I didn't think so either :-)
| Really it is just Klipper polling. It doesn't need this to determine the
| selection owner, it needs it as you said ti update its copy of the
| clipboard. It sucks...
This should probably be reported to the klipper people.
(don't poll.. wait for a new XSelSelectionOwner with a new timestamp)
One other thing though:
Currently we handle selection done with the keyboard differently from
selection done with the mouse.
Mouse uses XSetSelectionOwner, Key doesn't.
Is this possible to change so that they work the _exact_ same way. (as
in end result)
--
Lgb
