[Development] QtQuick Layout behavior changes?

[André Somers]

Hi,

On 27/02/2024 02:46, Jan-Arve Sæther via Development wrote:
>
> Hi Nicolas.
>
>
> Thank you for your concern. I've explained the reasoning in the issue 
> here:
>
>
> https://bugreports.qt.io/browse/QTBUG-117597
>
Well, it appears as if the reasoning in that issue is still concerned 
with the effects on existing UI's, but unless I am missing something, 
that concern seems to have not actually materialized in the actual work 
that has been done. Behavioral changes like this surely should be opt-in?

Cheers,

André


>
> Jan Arve
>
>
> *From: *Development <development-bounces at qt-project.org> on behalf of 
> Nicolas Fella via Development <development at qt-project.org>
> *Date: *Monday, 26 February 2024 at 17:15
> *To: *development at qt-project.org <development at qt-project.org>
> *Subject: *[Development] QtQuick Layout behavior changes?
>
> Hi,
>
> after updating my local Qt 6.7 + KDE build I noticed a number of severe
> UI bugs in various QML-based programs (Plasma, System Settings, several
> applications) where certain elements are wrongly sized. Investigating
> lead me to 
> https://bugreports.qt.io/browse/QTBUG-117597<https://bugreports.qt.io/browse/QTBUG-117597>, 
> which suggests
> to me that there is a deliberate change in the behavior of layouts
> causing these issues. Surely this can't be the case, can it? This would
> cause countless regressions in the UI of just about every piece of QML
> software written before this change and completely go against Qt's
> stability guarantees. Could someone please shed some light on this and
> explain whether I'm misunderstanding the situation or there is a massive
> breaking change coming our way?
>
> Cheers
>
> Nico
>
>
> -- 
> Development mailing list
> Development at qt-project.org
> https://lists.qt-project.org/listinfo/development<https://lists.qt-project.org/listinfo/development>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20240227/6ece9898/attachment-0001.htm>