On Sun, Dec 20, 2020 at 11:39:15PM +0000, Thorsten Glaser wrote: > Thomas Dickey dixit: > > >I'm guessing that it's timing, e.g., xterm could wait a few milliseconds > >to retry and then give up on that loop, in case the window events don't > >arrive rapidly enough. > > “rapidly enough” as criterium isn’t going to help everyone. > > We have multi-GHz desktop bolides, few-MHz m68k/SPARC/POWER/… machines, > and running X11 over various network protocols (X, VNC, RDP, NX, x2go), > with varying latencies. > > If the solution for this issue with XCheckWindowEvent is dependent on > such things, I’d argue that not using XCheckWindowEvent is the correct > fix instead ☺
I'm aware of that. It's called a "dilemma" (in this case, a bug which I'm easily able to reproduce versus one that I'm not). Since I'm able to reproduce the case with the active-icon, I might decide to use XCheckWindowEvent with a timeout for that scenario and the XWindowEvent for the other. -- Thomas E. Dickey <dic...@invisible-island.net> https://invisible-island.net ftp://ftp.invisible-island.net
signature.asc
Description: PGP signature
