<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#c44">Comment # 44</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:bugzilla2@cb-computerservice.at" title="bugzilla2@cb-computerservice.at">bugzilla2@cb-computerservice.at</a> <pre>> 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. Since this would only slow down the first start with a new Icon Set, that would be acceptable in my opinion. If Icon quality increases thats the way LibO should go. Of course I would mention such a change in the NEWS for that release... > 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). Sounds great :) But until then, a one time only slower start should be fully acceptable to users.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>