public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Harold L Hunt II <huntharo@msu.edu> To: cygx <cygwin-xfree@cygwin.com> Subject: XFree86-xserv-4.3.0-36 Date: Sun, 11 Jan 2004 03:59:00 -0000 [thread overview] Message-ID: <4000CA1C.2010000@msu.edu> (raw) A new 'test' version has been posted with many changes to the clipboard support. The new version includes a fix for calling OpenClipboard without calling CloseClipboard, which makes the Win32 clipboard inaccessible to other applications until we call CloseClipboard later when something is selected in X11. I have now identified the following things that need to be changed before this series of releases can be marked as 'curr': 1) [Easy] When aborting processing of a SelectionRequest message, be sure to send a SelectionNotify event to the requesting X Client, telling them that no selection data is available. Currently we are not sending a response in several cases, which is a broken way to do things. 2) [Medium] Perhaps add some protections to our call to XPeekIfEvent to make our predicate function return TRUE if a timeout happens. We might be able to do this by setting up a timer event (if these are supported, I suspect they are) and having our predicate function return TRUE for both the SelectionNotify event and/or our timer expired event. The reason to do this is that an X11 Client that misbehaves like we do in #1 (not sending a SelectionNotify in response to a SelectionRequest) will cause our clipboard thread to block indefinitely. This will eventually lead to a crash. 3) [Hard] Release ownership of the X11 selections if an unsupported format is copied to the Win32 clipboard. It will be difficult to do this without triggering infinite loops in our code that monitors changes in ownership of the X11 selection. It is, however, quite possible to do. Harold
reply other threads:[~2004-01-11 3:59 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=4000CA1C.2010000@msu.edu \ --to=huntharo@msu.edu \ --cc=cygwin-xfree@cygwin.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).