Antwort: Clipboard fix - Please test

[Ben Jackson]

Yep, this stop's things from hanging indefinitely (ie they now only hang for
3 secs) but after the 3 secs it still doesn't paste into the app. This is
only broken for pasting from X->Windows and NOT vice versa. Win->X is fine
(as is X->X) and works a treat, but X->win hangs for 3 seconds ...

I guess this is an improvement, but doesn't resolve the issue of it not
pasting the text. 
Here's my XWin.log now:
winClipboardProc - DISPLAY=127.0.0.1:0.0
winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened
the display.
winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the
display.
winClipboardProc - XOpenDisplay () returned and successfully opened the
display.
winClipboardWindowProc - WM_DRAWCLIPBOARD - Initializing - Returning.
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winMultiWindowXMsgProcErrorHandler - ERROR: BadWindow (invalid Window
Parameter)
winMultiWindowXMsgProcErrorHandler - ERROR: BadWindow (invalid Window
parameter)
winMultiWindowXMsgProcErrorHandler - ERROR: BadWindow (invalid Window
parameter)
winMultiWindowXMsgProcErrorHandler - ERROR: BadWindow (invalid Window
parameter)
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winMultiWindowXMsgProcErrorHandler - ERROR: BadWindow (invalid Window
parameter)
winMultiWindowXMsgProcErrorHandler - ERROR: BadWindow (invalid Window
parameter)
(END)

thanks for looking at this.

Ps: I was copying text from nedit to any windows app, ill try some other
apps and other datatypes.


-----Original Message-----
From: cygwin-xfree-owner@cygwin.com [mailto:cygwin-xfree-owner@cygwin.com]
On Behalf Of Harold L Hunt II
Sent: 25 March 2004 16:11
To: cygwin-xfree@cygwin.com
Subject: Re: Antwort: Clipboard fix - Please test

Andreas,

Andreas_Vogler@msg.de wrote:
> Hallo,
> I have had an freeze with the .60 Cygx Relase and IBM Personal 
> Communication, it has freezed when Coping somthing in IBM PC just after 
> copying somting in cygwin. (IBM PM Was freezed completly, Cygwin wasnt 
> able zu shutdown.)
> 
> Now with the 61 Release IBM PM freeze for about 2-3 Sek than all works 
> again normaly, so i coult say it has gotten better.

Okay, that is pretty much how it should work.

I set the timeout to 3 seconds when we don't get the reply that we are 
looking for.  I will probably tune that now down to 1 or 2 seconds... in 
fact, I can probably drop it to 0.5 seconds since we do call XSync 
before waiting for events, so our reply should always be waiting for us 
when we look for it.

Harold