<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Icons are corrupted on Windows when scaling UI 150% and higher, with some OpenGL dependency" href="https://bugs.documentfoundation.org/show_bug.cgi?id=119020#c43">Comment # 43</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Icons are corrupted on Windows when scaling UI 150% and higher, with some OpenGL dependency" href="https://bugs.documentfoundation.org/show_bug.cgi?id=119020">bug 119020</a> from <a class="email" href="mailto:glogow@fbihome.de" title="Jan-Marek Glogowski <glogow@fbihome.de>"> Jan-Marek Glogowski</a> <pre>(In reply to V Stuart Foote from <a href="show_bug.cgi?id=119020#c41">comment #41</a>) > On Windows 10 Pro 64-bit (1803) en-US with nVidia GTX 750ti with 3840x2160 > 40" (~110.15 dpi) > Version: 6.2.0.0.alpha1+ > Build ID: 4fa9e6f7f891b335ae1b432e0848c1e46c8fe3ef > CPU threads: 8; OS: Windows 10.0; UI render: GL; VCL: win; > TinderBox: Win-x86@42, Branch:master, Time: 2018-10-30_22:44:48 > Locale: en-US (en_US); Calc: CL > > With OpenGL rendering enabled and scaling UI to 300% to force LO icon > scaling--all of the icon themes scale cleanly if a bit pixelated but without > any color corruption. Will check a 64-bit build (TB42 or TB62) when one > rolls. Ok. Just set the bug to resolved - verified. I assume there is no difference, otherwise the problem is totally different and would need an extra bug IMHO. > @Jan-Marek, Tomaž -- notice we've been using the "BMPScaleFlag::Fast" [1], > any reason not to use Lanczos or at least BiCubic to reduce pixelation since > these scaled icon themes are being cached to user profile on first launch? > Better at least until SVG themes can be finished. We can change the scaling from ::Fast to ::Default or ::BestQuality. No idea how much this would prolong the first start. So I'm a bit reluctant to just change the value, as I can see the bug reports coming in that LO startup time has increased. Unless we implement scaling as a completely asynchronous background job, which can dynamically update any images (which would also be cool to have for document open times with many images of any kind, which need scaling for zoom level, also PDF or SVG). Eventuality it would also be good to convert all icons as a background job and store them in a zip again. That should still be faster then a single file access, even with unzip, then all those small files. But both ideas are a whole new story and the 2nd depends on the 1st. > And assuming 64-bit also is also good, can this be back ported for 6.1.4? I'll do backports for 6.1 and 6.0, even if 64bit still has problems, as it definitely solves them for 32bit. 6.0.7 is due this week / Thursday I think, so no more time left for 6.0. It's simple enough to get accepted this late IMHO.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>