I just started using 2.3.1-rc6 and am seeing lots of the following messages in the log:

9/9/08 Sep 9, 2008  11:16:39 AM [0x0-0x17017].org.x.X11[150] DarwinPressModifierKey bad keycode: key=5

9/9/08 Sep 9, 2008  11:16:42 AM [0x0-0x17017].org.x.X11[150] DarwinPressModifierKey bad keycode: key=7

9/9/08 Sep 9, 2008  11:21:50 AM [0x0-0x17017].org.x.X11[150] mieqEnequeue: out-of-order valuator event; dropping.

Sorry if this is old news.

I've gotten one crash today, when using gnome-terminal and emacs-23 (not sure if related to above).  Is it necessary for me to recompile things in Macports which link into X11 (e.g., gtk+2)?  I was using 2.2.1 when I compiled my Macports stuff.

Thanks,
Bob

On Sat, Sep 6, 2008 at 1:40 AM, Jeremy Huddleston <jeremyhu@apple.com> wrote:
Yes, I know I *JUST* released rc5, and I know I said that was pretty much it...  but I ended up fixing a bug yesterday that some users have been patiently waiting for for some time now, so I decided to not make them wait much longer for it.

http://static.macosforge.org/xquartz/downloads/X11-2.3.1_rc6.pkg

2.3.1_rc6 adds the following over rc5:

256 Color support*
Stability improvements in the file-descriptor handoff from /usr/X11/bin/Xquartz to X11.app

If these two issues don't really impact you, then there's not really a need for you to try out rc6 if you have rc5 already.

Thanks,
Jeremy


*: kinda... there's a bug in the colormap processing if you are in TrueColor mode, but it works fine if you select '256 Color' from the X11->Preferences->Output->Colors, but that never wasn't working on Tiger, so this gets us to atleast where Tiger was.
_______________________________________________
Xquartz-dev mailing list
Xquartz-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev