[Development] [Releasing] HEADS-UP: Qt 5.15 Feature Freeze is in effect now

[Timur Pocheptsov]

Correct, to avoid breaking old connection syntax silently (with warnings not noticed in code).
Now, please enumerate those many modules you are talking about? There are 4 classes in
QtNetwork doing similar changes  (not touching a tricky signal, but a getter) and I, as the
maintainer of QtNetwork, prefer it this way.

Best.


________________________________
From: Development <development-bounces at qt-project.org> on behalf of Alexander Akulich <akulichalexander at gmail.com>
Sent: Wednesday, February 5, 2020 6:41 PM
To: Thiago Macieira <thiago.macieira at intel.com>
Cc: Qt development mailing list <development at qt-project.org>
Subject: Re: [Development] [Releasing] HEADS-UP: Qt 5.15 Feature Freeze is in effect now

On Wed, Feb 5, 2020 at 6:58 PM Thiago Macieira
<thiago.macieira at intel.com> wrote:
>
> The correct signal for an error situation is errorOccurred, like in
> QLocalSocket and QProcess.

Actually both QLocalSocket and QAbstractSocket renamed the "error()"
getter to keep using "error()" signal as opposed to many other Qt
modules "errorOccurred()" signals.
_______________________________________________
Development mailing list
Development at qt-project.org
https://lists.qt-project.org/listinfo/development
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20200205/afe65f85/attachment-0001.html>