[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mandrake-cooker
Subject:    Re: [Cooker] GNOME 2.2.1 Desktop
From:       Greg Meyer <gkmeyer () nysscpa ! org>
Date:       2003-03-19 0:12:11
[Download RAW message or body]

On Tuesday 18 March 2003 02:28 pm, Jan Ciger wrote:
> > > You do get the same error when running the same app directly (without
> > > Xnest or VNC) ? Then how come that the antialiasing works, when it does
> > > not have Render ? Either I am missing something or we do not understand
> > > each other.
> >
> > oops should have said I don't get... my bad.
>
> Aha, but that just reinforces my suspicion, that Qt may be broken. Anybody
> brave enough to recompile it with -no-xrender -no-xft ?
>
Based on your suspicions, I went back to look at the spec file for qt.  the 
diff between 3.1.1-12 and 3.1.1-13 contain this:

+# Laurent - 3.1.1-13mdk - default aa
+Patch16:qt-3.1-use-aa-by-default.patch.bz2
+



Here is the contents of patch 16

-bool qt_has_xft = FALSE;
-bool qt_use_antialiasing = FALSE;
+bool qt_has_xft = TRUE;
+bool qt_use_antialiasing = TRUE;

 static inline float pixelSize( const QFontDef &request, QPaintDevice 
*paintdevice,
        int scr )
@@ -2896,8 +2896,8 @@ void QFont::initialize()
 #endif // QT_NO_CODECS

 #ifndef QT_NO_XFTFREETYPE
-    qt_has_xft = FALSE;
-
+    qt_has_xft = TRUE;
+    qt_use_antialiasing = TRUE;
     if (qt_use_xrender &&
 XftInit(0) && XftInitFtLibrary()) {
 QSettings settings;


Tonight, I am going to try and reverse the patch, build it and see if that 
fixes the problem. 
-- 
Greg

[prev in list] [next in list] [prev in thread] [next in thread]