Re: more antialiased text fun

VV> I just redid the antialiased text/xrender patch against the latest on VV> the 21.2 branch; everything mostly works. VV> It's available at http://www.intrepid.com/~vladimir/xemacs_beta_aa.patch.gz . This uses the Render extension present in XFree86 4.02? VV> The fonts are specified now in normal XLFD fashion, and the code will VV> attempt to find a truetype font that can be rendered antialiased first, VV> and if it fails, will fall back to core fonts. VV> However, I'm having some expose/redraw issues. When an expose event is VV> received, most of the time the relevant portions of the frame don't VV> get redrawn. Is there some sort of pixmap caching going on, so that VV> x_output_string doesn't always get called? Strangely enough, if I VV> slowly drag a window over the xemacs window, the letters do mostly VV> get redrawn as they appear, but if I speed up the dragging, then VV> nothing gets redrawn. Note that this only happens if the window is VV> obscured by another window, and then uncovered -- everything updates VV> correctly from events inside the window (text editing, moving, selecting, VV> etc.). Hitting C-l always causes the window to render correctly. There are many redisplay bugs that have been around for years. Most of them are fairly minor. I would like to fix them, but I don't understand that code, and would probably spend a lot of time rewriting it. It would be great if someone would decide to "fix redisplay". Vladimir, you are encouraged to take up that role. VV> There's also an issue with the tabs -- I put in patch to xlwtabs.c to VV> avoid crashing if the font that was passed in was NULL (which shouldn't VV> happen, but crashes shouldn't happen either :-) and then code VV> in glyphs-x.c, which when setting the font for the tabs will check if VV> an Xft font is in use, and if it is, it will attempt to get an VV> equivalent core font from the library and use that. This works (the VV> tabs get displayed fine), but XEmacs then every once in a while VV> spews XConfigWindow errors and locks up (easily repeatable). I haven't VV> had a chance to track this one down, but hiding the tabs gets rid of VV> this problem. I still usually build --with-widgets=no ... VV> Any help into either issue would be appreciated... also if anyone VV> wants to give this code a shot but needs help setting things up, feel VV> free to email me.. Vladimir, you are welcome to become more of a core XEmacs developer. See http://cvs.xemacs.org/#committers. (I won't personally have time to look at your changes)