Skip to content

Conversation

@Vekhir
Copy link
Contributor

@Vekhir Vekhir commented Aug 27, 2024

In the upcoming Qt 6.8 release, several deprecations and changes are made. In preparation for that, this PR resolves the emitted warnings when building with Qt 6.8 Beta 3.

Except for the new permissions system introduced in 6.8, the changes modernise the current code and adopt current best practices.

The permissions system changes how Qt handles permission requests from websites. Most importantly, it saves the permissions itself, so we don't have to.
Tested with permission.site. All new code is enclosed in preprocessor directives, as is the old permission management, to remove it with Qt 6.8+.

Builds fine with Qt 6.7.2, Qt 6.8 Beta 3, Qt 5.15.14.

@Vekhir Vekhir force-pushed the fix-qt6.8-warnings branch from 0232d4f to 5624946 Compare February 12, 2025 15:28
Vekhir added 3 commits August 21, 2025 23:53
Qt 6.8 introduces a new system to manage permissions for websites

Building with Qt 6.7 and earlier is unaffected due to extensive preprocessor directives.
The old version of setContent returns bool and takes in pointers
to allow access to the error information. This was replaced in Qt 6.5
with a ParseResult struct which allows boolean checking and direct
access to the information without additional pointers.

The old version had separate overloads to specify whether to use
namespace processing or not. This, among other options, can now be
specified via ParseOptions which were introduced in Qt 6.5 too.
QDateTime::setTimeSpec is deprecated in Qt 6.9 per documentation,
but already emits a warning in Qt 6.8. Anyway, use setTimeZone.
@Vekhir Vekhir force-pushed the fix-qt6.8-warnings branch from 5624946 to 0e7a184 Compare August 21, 2025 22:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant