t bit of useful info. There's a benefit of
having all the docs in a self-contained
set as well.
-Topi
From: Development on behalf of Paul
Wicking via Development
Sent: Friday, September 15, 2023 11:25 AM
To: Edward Welbourne
Cc: development@qt-project.org
S
On 15 Sep 2023, at 10:44, Edward Welbourne via Development
wrote:
On 9/15/23 09:36, Kai Köhne via Development wrote:
The methods are formally marked as deprecated for Qt 6.10. But the
methods are already in the '-obsolete' page for Qt 6.6, which leaves
the API in a weird in-between state.
Chr
On 9/15/23 09:36, Kai Köhne via Development wrote:
>> The methods are formally marked as deprecated for Qt 6.10. But the
>> methods are already in the '-obsolete' page for Qt 6.6, which leaves
>> the API in a weird in-between state.
Christian Kandeler (15 September 2023 10:31) wrote:
> Radical ide
On 9/15/23 09:36, Kai Köhne via Development wrote:
The methods are formally marked as deprecated for Qt 6.10. But the methods are
already in the '-obsolete' page for Qt 6.6, which leaves the API in a weird
in-between state.
Radical idea: Treat all deprecated functions as if they didn't exist,
Köhne
via Development
Sent: Friday, September 15, 2023 9:36 AM
To: qt-development
Subject: [Development] How to document API only deprecated in future Qt versions
Hi,
Eddy and Ivan did a great job in documenting how to formally deprecate API in
at https://wiki.qt.io/Deprecation . It's not
Kai Köhne (15 September 2023 09:36) wrote:
> I see why this 'conservative' approach is beneficial. Projects like Qt
> Creator tend to support multiple Qt versions, and immediately
> deprecating an old API in the same version the replacement API got
> added makes this hard to handle.
Note that QT_W
Hi,
Eddy and Ivan did a great job in documenting how to formally deprecate API in
at https://wiki.qt.io/Deprecation . It's not only giving you the right macros
to use ... it also contains some suggestions for which version to do it.
About the Qt version to deprecate an API for, the page says:
