public inbox for cygwin-xfree-announce@sourceware.org help / color / mirror / Atom feed
From: "Harold Hunt" <huntharo@msu.edu> To: "cygx" <cygwin-xfree@cygwin.com>, "cygxannounce" <cygwin-xfree-announce@cygwin.com> Subject: Updated on sourceware: XFree86-xserv-4.2.0-7 Date: Fri, 21 Jun 2002 22:36:00 -0000 [thread overview] Message-ID: <NHEELHJHHFKPMAEAFMFCMEBMDAAA.huntharo@msu.edu> (raw) The XFree86-xserv-4.2.0-7 package has been updated in the Cygwin distribution. This is a synchronization with all the fixes that have been applied through Server Test Series - Test 60. These fixes are listed below: 1) InitOutput.c, XWin.man, win.h, winwndproc.c - Add the -lesspointer command line parameter which causes Cygwin/XFree86 to hide the Windows mouse cursor when the mouse is over any Cygwin/XFree86 window (whether activated or not). (Stuart Adamson) 2) win.h, xc/config/cf/cygwin.cf - Stop building RANDR and disable Cygwin/XFree86's LAYER support. These two extensions were causing KDE 3.0 icons with alpha channels to not display. RENDER is still enabled. (Harold Hunt) 3) xc/programs/Xserver/os/osinit.c - Don't close the stdin, stdout, stderr file handles on Cygwin. We are no longer a command-line application so stdin, stdout, and stderr point to our first three file handles, rather than to their usual locations. This keeps the log file from being closed when you run XWin.exe with 'start XWin.exe'. (Stuart Adamson) 4) winwndproc.c - Call TrackMouseEvent to setup tracking for the WM_MOUSELEAVE message. When we see a WM_MOUSELEAVE message we show the cursor if we are hiding it. This will prevent cursors from disappearing when using the -lesspointer parameter. (Harold Hunt) 5) Do a clean before rebuilding the server to ensure that the RENDER extension is compiled in and enabled. The RENDER extension is now reenabled. Unfortunately, the RENDER extension is the cause of the display problem with KDE 3.0 icons that have alpha channels at a depth of 32 bits per pixel. It was previously thought that the LAYER and RANDR extensions were causing the problem because a rebuild of the server with RENDER enabled did not actually have RENDER enabled, thus making it seem that RENDER was not causing the problem. (Harold Hunt) 6) wincreatwnd.c - Remove a seemingly erroneous return from winCreateBoundingWindowFullScreen when we are using the Shadow GDI engine. This return was before we called UpdateWindow and BringWindowToTop. This seems to have snuck in at some point during merging of my local 4.2.0 and main trees. (Harold Hunt) -- Harold Hunt To update your installation, click on the "Install Cygwin now" link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Save it and run setup, answer the questions and pick up 'XFree86-xserv' from the 'XFree86' category. You may need to click the "Full" button if it doesn't show up. Note that downloads from sources.redhat.com (aka cygwin.com) aren't allowed due to bandwidth limitations. This means that you will need to find a mirror which has this update. In the US, ftp://archive.progeny.com/cygwin/ is a reliable high bandwidth connection. In Japan, ftp://ftp.u-aizu.ac.jp/pub/gnu/gnu-win32/ is usually up-to-date. In DK, http://mirrors.sunsite.dk/cygwin/ is usually up-to-date. If one of the above doesn't have the latest version of this package you can either wait for the site to be updated or find another mirror. Please send questions or comments to the Cygwin/XFree86 mailing list at: cygwin-xfree@sources.redhat.com . If you want to subscribe go to: http://cygwin.com/lists.html I would appreciate if you would use this mailing list rather than emailing me directly. This includes ideas and comments about the setup utility or Cygwin/XFree86 in general. If you want to make a point or ask a question the Cygwin/XFree86 mailing list is the appropriate place.
reply other threads:[~2002-06-22 5:36 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=NHEELHJHHFKPMAEAFMFCMEBMDAAA.huntharo@msu.edu \ --to=huntharo@msu.edu \ --cc=cygwin-xfree-announce@cygwin.com \ --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).