-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use Fusion style on Windows 10+ #19051
Conversation
Preliminary testing, all seems ok & |
Why isn't there any kind of explanation/justification* in the description for this change? *I know that this has something to do with Qt 6.5 but a fuller explanation is needed for the choice. |
@sledgehammer999 Qt have been recommending/suggesting the use of It addresses issues like #13603 -> #13603 (comment) Some more info: |
Oops... Related issues have been touched upon in various topics for a long time, so I felt too "merged" with its existence. Thank @xavier2k6 for summarizing it here. |
FYI, this is true only for Qt5. The Qt6 docs don't have this recommendation. IIRC one of the key aspects of Qt6 was that it had far better High DPI Support compared to Qt5. Moreover, I don't think it is appropriate to stop supporting native look on Windows. |
They aren't going to do that IMO
https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qt/6.5.0/release-note.md
But they are recommending it as I pointed out in #19051 (comment) (at least for proper dark mode support)
|
So it isn't fully "native" to latest Windows versions.
In addition, qBittorrent itself has quite a lot of custom elements in its design. |
@xavier2k6 |
Another option would be to allow it as
We've been doing that or at least I have countless times..... & we sill still have users asking can it be enabled through config file etc. -> #17081 (comment)
Totally agree! TBH - I think there's just too many benefits to go with |
Let's wait a couple of days for other people input regarding native look (or not). |
I would produce a beta release with it and explicitly mentioned it on the news page (with an indication of its supposed advantages and possible disadvantages). Then it would be more likely to get feedback from a slightly wider range of users. But I'm not rushing to merge it anyway. |
It affects only the style used by default. You can still override it using |
There doesn't seem to be any new discussion here. @glassez it's your choice if you want to merge it and let it be tested for the next beta release. Or wait for any Qt progress on the matter. We can stick to 6.4.x for the time being. |
This PR isn't restricted Qt version to be at least 6.5. Anyway we should stick to 6.4.x on Windows until "crash on exit" issue is fixed. |
I think it would be a good idea to have this in the next public beta release?! |
I decided to postpone it for now. Moreover, we cannot yet get all the benefits from using Qt 6.5, along the way without introducing a lot of its regressions and shortcomings. |
This comment was marked as resolved.
This comment was marked as resolved.
PR is rebased to resolve merge conflicts. |
Re-tested. 👍 |
Now I intend to merge it in master so that it has more time to be tested (at least by a small number of users that use alpha builds). |
This comment was marked as off-topic.
This comment was marked as off-topic.
@stalkerok This has nothing to do with the |
What about 6.6.1? |
It still happens there as it's a change in Qt's theme handling behavior......we will have to adapt/make necessary changes. The highlight bar was changed many moons ago I believe for the WebUI to a fixed color/not follow system etc., similar may have to be done going forward for GUI too. As it stands....issues that were brought up when we were changing icon colors etc. (like not being able to see icon when highlighted) are now again an issue depending on So, you can see why it's not so easy to make certain aesthetic changes. |
No description provided.