Update Bauh to Qt 6.6.2 #370
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@PrivateN00b thanks for your effort in converting the current code base to QT6. I'll retest everything to make sure we don't have regressions, so it may take some time... |
|
Brilliant job here, looking forward for the Qt6 version ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updating from Qt5 to Qt6 mostly took attribute call changes, going from exec_() to exec() and finding a solution for the removed QDesktopWidgets class with QScreen.
I haven't tested all the functionalities, like flatpak building for example or checking all the setting options hand-by-hand. Installing/uninstalling apps, searching for packages, changing some searchbox options, going through settings tabs, getting recommended packages and others are working on my machine, but most likely we would need to atleast check the Flatpak building as well atleast if my updated code seems to be alright.
Related issue: #359