<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Harmonize UI in Options-LibreOffice-View when works a Skia black list" href="https://bugs.documentfoundation.org/show_bug.cgi?id=137159#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Harmonize UI in Options-LibreOffice-View when works a Skia black list" href="https://bugs.documentfoundation.org/show_bug.cgi?id=137159">bug 137159</a> from <a class="email" href="mailto:l.lunak@collabora.com" title="Luboš Luňák <l.lunak@collabora.com>"> Luboš Luňák</a> <pre>- The option is called 'force'. The opposite of forcing is not forcing the other way, it's letting things be. So there's no UI problem. - If LO detects the HW is problematic, then it just should be disabled and an easy checkbox to ignore that is just a recipe for problems. If the user is knowledgeable enough there's the expert configuration or SAL_FORCESKIA, and if the user is not knowledgeable then they shouldn't be messing with things. - How would that actually work technically? Let's stay LO starts and detects problematic HW, but the option is unchecked. How will LO know whether the option is unchecked because you unchecked it or because it's never been checked? How do options why are they unchecked?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>