RE: Mouse dragging slow in XWin-Test56 with -emulate3buttons

[Bradey Honsinger <BradeyH at construx dot com>]

I think the only reason that I set the timeout so high was because it wasn't
working--I vaguely remember having trouble getting the simultaneous button
presses to work, which makes sense now. If the timeout was always 1ms, no
wonder I had trouble! 

An error message in the log certainly wouldn't hurt, but I think it'll be a
rare enough problem that there's probably no real need. Anyone who would
read the log would probably check the list, anyway. If anything, I'd
probably put a note in the documentation (Table 3-1) or the FAQ (question
3.4) to the effect of: 

"Note: setting the timeout too high (>100ms) will make it difficult to drag
windows or select text, since XWin will wait to process the button1-down
event until it's sure that it's not a button3-down event." 

That's all pretty obvious now that I realize what's going on, but it took me
a while to figure it out.

- Bradey


-----Original Message-----
From: Stuart Adamson [mailto:stuart.adamson@evolution.net]
Sent: Thursday, June 27, 2002 3:00 AM
To: 'cygwin-xfree@cygwin.com'
Subject: RE: Mouse dragging slow in XWin-Test56 with -emulate3buttons


> I didn't diff the sources, but it sounds like XWin was never using the
> timeout parameter to -emulate3buttons until this typo was 
> fixed.

Worse than that - XWin was ignoring the parameter and also the default
50ms and setting the timeout to 1 millisecond.

> In any case, even if it is a bug, I don't need a fix

We could ErrorF("emulate3buttons timeout >100ms.  Is this really what you
want?");

but how many people would read /tmp/XWin.log to see that this is a problem?


Stuart