[okular] [Bug 409644] [Wayland] Panning in Okular is laggy with 4K monitor

[Filzmaier Josef]

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

--- Comment #8 from Filzmaier Josef <j.filzmaier at gmx.at> ---
I couldn't yet find a solution to the probelm, a few questions though:

https://invent.kde.org/graphics/okular/-/blob/master/core/document.cpp#L1519
Why is devicePixelRatio here forced to be 1 instead of
QScreen::devicePixelRatio()?

If enabling PAGEVIEW_DEBUG=true the build fails because kWarning does not exist
on my machine. If this is a bug i could create a merge request that fixes this.

Is there a way to tell an application to use the scale of 225%, as configured
within the "Display and Monitor" KCM? QT_SCALE_FACTOR does not seem to have the
same effect.

----

When starting Okular it reports in the 225% Display Scale case:
org.kde.okular.core: sending request observer=0x560658c0b5d0 3582x5001 at 1 async
== true isTile == false
When starting in 100% Display Scale case:
org.kde.okular.core: sending request observer=0x5585941d7490 2688x3751 at 2 async
== true isTile == false


My suspicion is that the difference in requestRect size causes a problem here.
I'm still investigating how this size comes to be

On another note: Typing in values in the "Display and Monitor" KCM's "Scale"
Spinner directly is a really weird experience

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