<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Editing: The latency while scrolling with OpenGL enabled is a bit to high" href="https://bugs.documentfoundation.org/show_bug.cgi?id=113649#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Editing: The latency while scrolling with OpenGL enabled is a bit to high" href="https://bugs.documentfoundation.org/show_bug.cgi?id=113649">bug 113649</a> from <a class="email" href="mailto:vstuart.foote@utsa.edu" title="V Stuart Foote <vstuart.foote@utsa.edu>"> V Stuart Foote</a> <pre>(In reply to Telesto from <a href="show_bug.cgi?id=113649#c4">comment #4</a>) > > Setting GDI/GDI+ to default for the time being, dropping the 'active' > support for OpenGL, and focus more on accelerated hardware seems a logical > conclusion (to me) The route for hardware accelerating Windows builds would be through native DirectX and DirectWrite _not GDI+_ or legacy Uniscribe. The truth is, legacy GDI+ and GDI native implementation is becoming more unmaintainable as Microsoft moves the platform away from it. But cross-platform we've moved to HarfBuzz, and are looking at Freetype, with some skia support, as replacements for DirectWrite rendering on Windows. Similar choices in non-native implementations for macOS Quartz have been made. Its all pretty messy--but resources of the project prevent doing "native" development for the supported platforms. What can be done for the project is OpenGL implementation based.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>