[Digikam-devel] [digikam] [Bug 337231] use high resolution pixmaps on retina displays [patch]

[Axel]

https://bugs.kde.org/show_bug.cgi?id=337231

--- Comment #50 from Axel <arnolda747 at gmail.com> ---
(In reply to Robert Zeller from comment #48)

Strange, since Gilles said that it works ok for him. So it seems there is some
difference in how Qt renders pixmaps with higher resolution, which is not just
the rendering engine. Now, I wonder what makes the difference...

In any case, with the patch, it is disabled by default and works under Linux.

> I tried "native" and "raster" and there is no noticeable difference
> between the two. I can't use GL because that freezes my kde for some
> reason; a known behavior in openSUSE on some hardware.
> 
> On 08/17/2014 08:59 PM, Axel wrote:
> > https://bugs.kde.org/show_bug.cgi?id=337231
> >
> > --- Comment #46 from Axel <arnolda747 at gmail.com> ---
> > (In reply to Robert Zeller from comment #45)
> >
> >>  #cmakedefine by #define
> >>
> >> I again get the old problem: artifacts in regions with repeating regular
> >> structures and grainy preview.
> > Yes, that should be the case. My question was, if setting "export
> > QT_GRAPHICSSYSTEM native" (or replacing native with GL oder raster) before
> > running digikam does change anything. Usually, this environment variable is not
> > set, but it can be used to change the default renderer
> > (https://forum.kde.org/viewtopic.php?f=66&t=90821).
> >
> > As far as I understood, some distributions recently changed the default
> > renderer from "native" to "raster", and I would simply like to know whether the
> > the graphicssystem makes a difference. So, can you try through and see whether
> > the artifacts also disappear with one of the rendering systems?
> >
> > Thanks,
> > Axel
> >

-- 
You are receiving this mail because:
You are the assignee for the bug.