Re: Copy to clipboard for Linux

[Dave D. <dde...@es...>]

Daniel J Sebald <dan...@ie...> writes:

> Sure, but I think moving that XFlush() command to before sending an
> event to the requesting client puts us in the realm of reasonable
> understanding (Dave hasn't disagreed with that yet, I think)


If adding an XFlush() changes the behaviour, then IMHO there's a real
bug elsewhere in the code that's being masked. So I'd say that fact
that the flush changes things means we do not understand what is
happening.

The whole X thing was designed to be correct and deterministic in the face of
different clients with different latencies, etc (one client can be on
the LAN, and another can be on the other side of the world). So if one
has to resort to forcing flushing of packets, there's a problem
somewhere else.

> and at
> the same time [XFlush] appears to fix the problem. 

I don't believe it can fix the problem. I agree that it can drive the
symptom underground, but IMHO it's better to find and fix the real
bug.


If someone can summarise the problem, and simple steps to reproduce, I
can try to find some time to investigate. (Ideally, the steps would
not require KDE or gnome or such, since I generally just use fvwm.)

dd
-- 
Dave Denholm              <dde...@es...>       http://www.esmertec.com