Re: [Development] Qt 5.15.10 LTS Commercial released

[Tuukka Turunen]

Hi,

The release notes are stored within Qt Account (under Downloads, select 
Product: Qt and Version: 5.15.10), i.e. one needs to have a commercial license 
to see those.

Yours,

Tuukka

From: Development  on behalf of Milian 
Wolff via Development 
Date: Wednesday, 8. June 2022 at 0.53
To: development@qt-project.org 
Subject: Re: [Development] Qt 5.15.10 LTS Commercial released
On Dienstag, 7. Juni 2022 18:03:31 CEST Tarja Sundqvist wrote:
> Hi all,
>
> we have released Qt 5.15.10 LTS Commercial today. Please see the blog post:
> https://www.qt.io/blog/commercial-lts-qt-5.15.10-released

Hey there,

where are the "release notes" to be found which contain the "list of fixes and
the overview of all important changes"?

Please, can you add that directly to the release announcement in the future?

Thanks

--
Milian Wolff | milian.wo...@kdab.com | Senior Software Engineer
KDAB (Deutschland) GmbH, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt, C++ and OpenGL Experts
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Reminder: QtCS2022 - Agenda, BBB Link and Social Gathering

[Pedro Bessa]

Good morning!

We meet in 15 minutes at: https://meet.kde.org/b/qtcs2022-jun8


From: Development  on behalf of Pedro Bessa 

Date: Monday, 6. June 2022 at 12:47
To: development@qt-project.org 
Subject: [Development] Reminder: QtCS2022 - Agenda, BBB Link and Social 
Gathering
Reminder: we meet tomorrow at 9:30am CEST to start our 
QtCS2022!

BigBlueButton links to access our virtual event:
Jun 7: https://meet.kde.org/b/qtcs2022-jun7
Jun 8: https://meet.kde.org/b/qtcs2022-jun8

See you tomorrow! :)

From: Development  on behalf of Pedro Bessa 

Date: Friday, 3. June 2022 at 16:16
To: development@qt-project.org 
Subject: [Development] QtCS2022 - Agenda, BBB Link and Social Gathering
Hi again,

I hope you are all doing well.
Sorry for the spam! - here is one of my last pre-event e-mail messages. :)

BigBlueButton links to access our virtual event:
Jun 7: https://meet.kde.org/b/qtcs2022-jun7
Jun 8: https://meet.kde.org/b/qtcs2022-jun8
Break-out rooms can be created ad hoc.

Our Program is all 
scheduled already – we might have some small changes there.
We still have some free slots; let’s see if additional sessions emerge, if we 
move things around or if those free slots become Breaks.

Everything fits just one Track, so we will not have concurrent sessions.

Each Session has its own page now. So if you own a session, feel free to edit 
its page.

In case you are in Berlin: we propose to 
meet for some drinks and food 
after the Event. If you would like to join us, please reply to me directly! ;)

That’s all for now.
Thank you and enjoy your weekend!

Cheers,

Pedro Bessa
Community Relations Manager
The Qt Company
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Qt 5.15.10 LTS Commercial released

[Milian Wolff via Development]

On Dienstag, 7. Juni 2022 18:03:31 CEST Tarja Sundqvist wrote:
> Hi all,
> 
> we have released Qt 5.15.10 LTS Commercial today. Please see the blog post:
> https://www.qt.io/blog/commercial-lts-qt-5.15.10-released

Hey there,

where are the "release notes" to be found which contain the "list of fixes and 
the overview of all important changes"?

Please, can you add that directly to the release announcement in the future?

Thanks

-- 
Milian Wolff | milian.wo...@kdab.com | Senior Software Engineer
KDAB (Deutschland) GmbH, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt, C++ and OpenGL Experts

smime.p7s
Description: S/MIME cryptographic signature
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] QPushButton: drag and drop

[Giuseppe D'Angelo via Development]

Il 07/06/22 20:57, Laszlo Papp ha scritto:
Just checked the Qt wiki, but it does not seem to speak about this rule. 
Only binary and source compatibility. No behaviour compatibility. And by 
the way, fixing the bug to match the documentation and therefore 
intended behaviour would not even be behaviour break.


https://wiki.qt.io/Qt-Version-Compatibility 



There's behaviour break and behaviour break.

Here we're talking about a fundamental change to how Qt has (not?) 
handled mouse release notifications on DND. I can wager there's also 
other many other similar situations (e.g. while having the mouse grab, a 
widget gets hidden, or a modal window opens up, etc.) that are currently 
similarly unhandled. Bonus points for "user cancels DND with the 
keyboard (escape) and releases into the widget", "a modal window opens 
up and closes down while the user never releases the mouse", etc.



I'm calling it a "fundamental" change, because

* any widget currently handling DND already does not expect to receive 
any event when DND is done; this may cause a further bug, for instance a 
widget gets a mouse release when it thinks it never saw the 
corresponding press;


* any widget currently NOT handling DND (e.g. QPushButton) needs to 
handle the fake release event, in whatever way it's delivered.


which is a long way to say "any QWidget subclass handling mouse events 
needs to be changed". And that's a very high bar for a behavioral change.



If anything, this could start on a opt-in basis (a widget attribute set 
by the user, possibly also an application attribute, if you're feeling 
adventurous) and slowly starting fixing any misbehaving widget in the 
span of 2-3 minor releases, then we flip the attribute for next LTS (opt 
out instead of in), then it's the default in Qt 7.



My 2 c,

--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
KDAB (France) S.A.S., a KDAB Group company
Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com
KDAB - The Qt, C++ and OpenGL Experts


smime.p7s
Description: Firma crittografica S/MIME
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] QPushButton: drag and drop

[Laszlo Papp]

On Tue, Jun 7, 2022 at 3:26 PM David Skoland  wrote:

> “If it’s a bug people rely on, it’s a feature”
>

Just checked the Qt wiki, but it does not seem to speak about this rule.
Only binary and source compatibility. No behaviour compatibility. And by
the way, fixing the bug to match the documentation and therefore intended
behaviour would not even be behaviour break.

https://wiki.qt.io/Qt-Version-Compatibility
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] QPushButton: drag and drop

[Laszlo Papp]

On Tue, Jun 7, 2022 at 3:26 PM David Skoland  wrote:

> Hi,
>
> It is their problem if they have started relying on a bug.
>
>
> I don’t think this is a good way to approach this. When programming with a
> framework, you program based on the current behavior of that framework,
> regardless of what the “correct” behavior is supposed to be. I think it's
> pertinent to pull an insightful quote from Linus Torvalds here:
>
> “If it’s a bug people rely on, it’s a feature”
>

If your intention is to strengthen the argument for the bug with a famous
(or infamous, depending on one's point of view) personality, like Linus, or
anyone else, then I can say that it does not work for me. Just like it does
not work for the Darwin followers that Darwin rejected his idea on his
deathbed. That is because they are convinced by the idea objectively rather
than a personality, whose judgement can be subjective.


> Don’t get me wrong, this is definitely a useful discussion (thanks for
> bringing it up), but as I see it in light of Qt’s compatibility promises,
> drastically changing drag and drop behavior looks like a Qt7 point that
> should be further discussed. I personally think Shawn’s proposal seems very
> sensible at a glance.
>
> If I recall correctly, there was a list of major behavior changes for Qt6.
> If we decide to change this behavior, this point should probably be added
> to the Qt7 equivalent if one exists, in addition to an eventual porting
> guide.
>

Yes, I also suggested something similar on Discord to Volker, as far as I
can tell, that Shawn / Giuseppe before coming here for a discussion. It
does not look that it would warrant Qt 7 though. What makes you think so?

I personally think that not emitting the clicked signal, which was the
original concern, but releasing the widget would satisfy everyone here in
this discussion.
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Reminder: Codereview scheduled maintenance break on Monday 6-Jun 7 am CET

[Thiago Macieira]

On Monday, 6 June 2022 09:02:07 PDT Thiago Macieira wrote:
> On Monday, 6 June 2022 01:56:14 PDT Jukka Jokiniva wrote:
> > Fix was found and deployed. Maintenance break is over for Gerrit.
> 
> The previous Gerrit had the ability to add a short description of what a
> patchset was, which helped reviewers to know what you'd changed between
> patchsets. Gerrit still sets it if you edit the commit message.
> 
> But I can't find the ability any more. Does anyone know where it went?

Seems like we cannot add comments to changes that are in Staged state any 
more. We couldn't change votes in integrating changes before, but this appears 
to now happen to any comment at all.

Error 409 (Conflict): change is closed

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Cloud Software Architect - Intel DCAI Cloud Engineering



___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Qt 5.15.10 LTS Commercial released

[Tarja Sundqvist]

Hi all,

we have released Qt 5.15.10 LTS Commercial today. Please see the blog post:
https://www.qt.io/blog/commercial-lts-qt-5.15.10-released


Big thanks to everyone involved & have a nice summer!



Best regards

Tarja Sundqvist

Release Manager

___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] QPushButton: drag and drop

[David Skoland]

Hi,

It is their problem if they have started relying on a bug.

I don’t think this is a good way to approach this. When programming with a 
framework, you program based on the current behavior of that framework, 
regardless of what the “correct” behavior is supposed to be. I think it's 
pertinent to pull an insightful quote from Linus Torvalds here:

“If it’s a bug people rely on, it’s a feature”

Don’t get me wrong, this is definitely a useful discussion (thanks for bringing 
it up), but as I see it in light of Qt’s compatibility promises, drastically 
changing drag and drop behavior looks like a Qt7 point that should be further 
discussed. I personally think Shawn’s proposal seems very sensible at a glance.

If I recall correctly, there was a list of major behavior changes for Qt6. If 
we decide to change this behavior, this point should probably be added to the 
Qt7 equivalent if one exists, in addition to an eventual porting guide.

Cheers,
David Skoland

On 7 Jun 2022, at 08:47, Laszlo Papp mailto:lp...@kde.org>> 
wrote:

On Fri, Jun 3, 2022 at 11:08 PM Giuseppe D'Angelo via Development 
mailto:development@qt-project.org>> wrote:
Given the blame on that code shows no changes since Nokia times,
something just tells me that this has never worked properly and people
started 1) relying on the release to be never received

It is their problem if they have started relying on a bug. We cannot leave bugs 
around and stop fixing bugs because bugs have been released.

Moreover, not only has this not been documented to rely on, but in fact, even 
the opposite has been claimed by the Qt docs, so people really should not rely 
on the opposite of the design and documentation: 
https://doc-snapshots.qt.io/qt6-dev/qdrag.html#exec

"Other events are still delivered to the application while the operation is 
performed."

So, I feel like it is just to just fix the code as the documentation claims the 
behaviour.

So, yes, I agree with you that this is not something we should leave as is.
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] QPushButton: drag and drop

[Laszlo Papp]

On Fri, Jun 3, 2022 at 11:08 PM Giuseppe D'Angelo via Development <
development@qt-project.org> wrote:

> Given the blame on that code shows no changes since Nokia times,
> something just tells me that this has never worked properly and people
> started 1) relying on the release to be never received


It is their problem if they have started relying on a bug. We cannot leave
bugs around and stop fixing bugs because bugs have been released.

Moreover, not only has this not been documented to rely on, but in fact,
even the opposite has been claimed by the Qt docs, so people really should
not rely on the opposite of the design and documentation:
https://doc-snapshots.qt.io/qt6-dev/qdrag.html#exec

"Other events are still delivered to the application while the operation is
performed."

So, I feel like it is just to just fix the code as the documentation claims
the behaviour.

So, yes, I agree with you that this is not something we should leave as is.
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development