Adjustments for Qt 6.10 #336
Merged
Conversation
This file contains hidden or 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
Contributor
Author
|
cc: @mrbean-bremen |
mrbean-bremen
approved these changes
Jan 2, 2026
Contributor
mrbean-bremen
left a comment
mrbean-bremen
left a comment
There was a problem hiding this comment.
Thanks, that looks good!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This includes some adjustments for Qt 6.10 as I have worked to update the 3D Slicer application to use Qt 6.10. I specifically ran into the issue where QDir's mkpath signature changed with a new std::optional argument which when unhandled was resulting in the wrapping for this method being unavailable and causing a traceback in 3D Slicer where mkpath was being used from python.
Additional changes based on reviewing some items described at https://doc.qt.io/qt-6/whatsnew610.html.