https://bugs.documentfoundation.org/show_bug.cgi?id=167250
--- Comment #31 from Michael Weghorn <[email protected]> --- (In reply to V Stuart Foote from comment #26) > So I guess the question at this point would be if moving broadly from win32 > to the qt6 toolkit on Windows becomes the most viable approach to improving > LO look and feel on Windows 11. > > As Michael W. has noted, qt6 has robust support for a Fluent Design motif on > Windows builds, meaning a qt6 based weld of VCL is feasible and likely more > maintainable going forward. It is very appealing on its potential > improvement to assistive technology support with move to UIA from > IAccessible2 instrumentation. > > What would it really cost in dev refactoring effort, and would its > maintenance tail improve were we to do so? Current master already has experimental support for the qt6 vcl plugin on Windows since commit 4d3a291b5d2d8a2dbdae5aca0d5fd506b5d5b0b9 Date: Sat Mar 28 02:06:24 2026 +0100 Add Qt6 support for Windows , which is based on some preparatory refactoring. As of now, this needs to be enabled manually in local dev builds (autogen options '--enable-qt6 --enable-headless') and some further work is needed (e.g. bundling Qt itself as a "proper external" instead of requiring it to be preinstalled). Further investigating it is more interesting in combination with the use of native Qt widgets (see tdf#130857). (In reply to jan d from comment #29) > I guess the QT style in question is just called "Windows" and is made to > "look native on Windows" > (https://doc.qt.io/qt-6/qtquickcontrols-windows.html) without mentioning > Fluent Design (There is a separate, but not-yet-complete Fluent Style in qt) That particular link is for Qt Quick, while LO uses Qt Widgets. There's also a default Qt style for Windows for Qt widgets, however. As far as I know, the KDE community wasn't too happy with that one and they use their own Breeze style (also used on Linux) for their applications by default on Windows as well. In case of going with Qt, the specific style to use could still be decided/changed in the future. -- You are receiving this mail because: You are the assignee for the bug.
