> On 21 Jul 2022, at 14:23, Alexandru Croitor wrote:
>
> Hi,
>
>> - we make Qt Location available as versions that works with Qt 6 LTS
>> releases (ie we’ll have something that works with Qt 6.2, but won’t spend
>> time on making something that is tested against 6.3 or 6.4).
>
> Will there
On Thursday, 21 July 2022 00:54:28 PDT Volker Hilsheimer wrote:
> These would be observable, quantifiable measurements. And if one of the
> reason for those measurements is “there are very few people who can review
> build system changes”, then that’s a qualitative statement, getting to
> which see
Hi,
> - we make Qt Location available as versions that works with Qt 6 LTS releases
> (ie we’ll have something that works with Qt 6.2, but won’t spend time on
> making something that is tested against 6.3 or 6.4).
Will there be qtlocation git tags and separate branches for each 6.2 patch
relea
Hi,
Lauri Laanmets, Alex, Shawn and myself had a talk about the state of Qt
Location and next steps yesterday. Qt Location is not officially available for
Qt 6 yet, and here’s what we are going to do about it:
Lauri and others have done a fantastic job of porting most of Qt Location to Qt
6 a
Hi
> Also the machinery of QT_DEPRECATED_METHOD(method, major, minor, reason)
> expanding to nothing for some settings, and possibly different things
> for other settings, of QT_DEPRECATED_WARNINGS_SINCE and
> QT_DISABLE_DEPRECATED_BEFORE entails (thanks to the limitations of the C
> preprocessor)
On Wednesday, 20 July 2022 11:29:57 PDT Mattie Nejati wrote:
>> I’m Mattie, a Ph.D. student at the University of Waterloo and I’ve
>> been studying the code review process of build files in Qt. For
>> example, I’ve found that changes to build files are 2 to 4 times less
>> likely to be discussed du
Lars wrote:
>> So instead of
>>
>> #if QT_DEPRECATED_SINCE(6, 4)
>> QT_DEPRECATED_VERSION_X_6_4("Use size() or length() instead.")
>> inline qsizetype count() const { return d.size; }
>> #endif
>>
>> You’d have:
>>
>> QT_DEPRECATED_METHOD(qsizetype count(), 6, 4, "Use size() or length()
On 20 Jul 2022, at 16:50, Edward Welbourne wrote:
>> We noticed recently that some APIs had been wrapped in #if-ery on
>> QT_DEPRECATED_SINCE(major, minor) without having QT_DEPRECATED or one
>> of the QT_DEPRECATED_VERSION* macros prepended to the actual
>> declarations within that #if-ery. This
> On 21 Jul 2022, at 00:30, Thiago Macieira wrote:
>
> On Wednesday, 20 July 2022 11:29:57 PDT Mattie Nejati wrote:
>> I’m Mattie, a Ph.D. student at the University of Waterloo and I’ve been
>> studying the code review process of build files in Qt. For example, I’ve
>> found that changes to bui
"So instead of
#if QT_DEPRECATED_SINCE(6, 4)
QT_DEPRECATED_VERSION_X_6_4("Use size() or length() instead.")
inline qsizetype count() const { return d.size; }
#endif
You’d have:
QT_DEPRECATED_METHOD(qsizetype count(), 6, 4, "Use size() or length()
instead.”)
"
Hi,
it would be re
Hi Eddy,
On 20 Jul 2022, at 16:50, Edward Welbourne
mailto:edward.welbou...@qt.io>> wrote:
Hi all,
TL;DR: there's a new [[Deprecation]] wiki page, please review.
We noticed recently that some APIs had been wrapped in #if-ery on
QT_DEPRECATED_SINCE(major, minor) without having QT_DEPRECATED or
11 matches
Mail list logo