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

List:       mandrake-cooker
Subject:    Re: [Cooker] GNOME 2.2.1 Desktop
From:       scott chevalley <avalon () osguru ! org>
Date:       2003-03-18 18:33:06
[Download RAW message or body]

Jan Ciger wrote:

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>  
>
>>Jan,
>>   I get the same thing here in a regular window (ie my desktop)
>>anti-aliasing etc is working fine.  But only in vnc or Xnest do the qt
>>applications give this kind of error.  Same version of vnc in 9.0 works
>>fine.  So I don't suspect vnc.
>>    
>>
>
>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.
>
>  
>
>>If you do (and you are right, it is butt ugly) disable it you still get
>>this same error.  But again only in Xnest or vnc.
>>    
>>
>
>But you have to recompile Qt for that. If you just unset the option in KDE and 
>unset the environment variables for that (QT_XFT or something like that), 
>that does not help - Qt will not use antialiasing, but will still require it. 
>
>When you compile Qt, there is an option -xft and -xrender, which control this 
>behavior and both are on by default : 
>
>
>    -no-xrender ........ Do not compile XRender support.
> *  -xrender ........... Compile XRender support.
>                         Requires X11/extensions/Xrender.h and libXrender.
>
>    -no-xft ............ Do not compile Xft (anti-aliased font) support.
> *  -xft ............... Compile Xft support.
>                         Requires X11/Xft/XftFreetype.h and libXft.
>
>I guess, that on a display, which does not support XRender extension, code 
>linked again a library compiled with these on will fail. I think, that 
>neither VNC and XNest support it on their emulated displays.  
>
>Jan
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.2.1 (GNU/Linux)
>
>iD8DBQE+d2OCn11XseNj94gRAsM2AJ9pG0atggYJxilUVSTbDZWudwU0bgCgukUC
>5HxJYmyixLQI9rjHOze22zo=
>=BS+n
>-----END PGP SIGNATURE-----
>
>
>  
>
I do believe this worked for me recently... I think it became broken, at 
least that I noticed it, around RC1 or just afterwards...  and I know 
that kde apps, and Xft in general is supposed to automatically fall back 
to the normal rendering if the RENDER extension is not available...

scott



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