Re: oxygen style needs xrender?
Matthew Woehlke <[email protected]> Thu, 01 May 2008 12:09:29 -0500
| Newsgroups | gmane.comp.kde.devel.general,gmane.comp.kde.solaris |
|---|---|
| Message-ID | <[email protected]> |
Girish Ramakrishnan wrote: > Matthew Woehlke wrote: >> Sebastian Kuegler wrote: >>> Apparently this is also a runtime problem. I've seen the Oxygen style and >>> Plasma look funny on a SUNray box, where apparently XRender is not available >>> but (tried to be) used, resulting in LSD-like coloring of lots of widgets. >>> Not that it doesn't look cool, but it does not a match with the artistic >>> vision either. :-) >> Oxygen style? I didn't know that used xrender? Got a screenshot? > > I believe this is expected behavior. Without xrender, Qt does not > support antialiasing and some composition modes. Ah, ok, so it's indirect via using the nice painting features of Qt... > When no xrender is > detected, Qt just falls back to the Windows style. I guess kde needs to > do similar? > > You can test this on any machine using QT_X11_NO_XRENDER=1 ./myapp. AAIIIEE!!! Ok, that looks HORRIBLE! So, yeah, I guess when picking the default style we need to check for XRender and use some generic style if it isn't present. Is the case of "occasionally" having/not having XRender rare enough that we can allow a user-selected style (via the KCS) to override that behavior? Or should we always check unless -style was used? -- Matthew "The government is not trying to destroy Microsoft, it's simply seeking to compel Microsoft to obey the law. It's quite revealing that Mr. Gates equates the two." -- A government official >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<