On Wednesday 22 May 2024 06:38:28 GMT-3 Volker Hilsheimer via Development
wrote:
> As long as Qt is built with exception support
We don't support toggling that on and off any more and haven't for a while.
QtCore and QtGui are compiled with exceptions enabled; all the other modules
are not. In p
> On 22 May 2024, at 16:30, Volker Hilsheimer via Development
> wrote:
>
>> On 22 May 2024, at 13:20, Turtle Creek Software
>> wrote:
>>
>> When we posted this problem to the Interest list, Thiago replied that Qt is
>> not designed to pass along exceptions and we shouldn't rely on the overri
> On 22 May 2024, at 13:20, Turtle Creek Software
> wrote:
>
> When we posted this problem to the Interest list, Thiago replied that Qt is
> not designed to pass along exceptions and we shouldn't rely on the override
> to QApplication::notify. He later qualified that some parts of Qt should b
Hi Dennis,
> On 7 May 2024, at 21:05, Turtle Creek Software wrote:
>
> TurtleSoft posted on the Interest list earlier about problems we had with
> exception handling, and Thiago suggested I post here.
>
> Since the early 90s, our C++ code has had about 10,000 sanity checks which
> give an err
+1!!!
> On 22 May 2024, at 10:52, Jøger Hansegård via Development
> wrote:
>
> Hi all,
>
> I would like to nominate Tim Blechmann for approver rights in the Qt project.
>
> Since 2013, Tim has been an active contributor to Qt, providing strong
> patches and insightful reviews. Currently, he
+1
--Liang
From: Development on behalf of Jøger
Hansegård via Development
Sent: Wednesday, May 22, 2024 10:52 AM
To: development@qt-project.org
Subject: [Development] Nominating Tim Blechmann for approver
Hi all,
I would like to nominate Tim Blechmann for app
Hi all,
I would like to nominate Tim Blechmann for approver rights in the Qt project.
Since 2013, Tim has been an active contributor to Qt, providing strong patches
and insightful reviews. Currently, he is doing excellent work on the GStreamer
backend in Qt Multimedia.
Changes owned:
* https:/
I agree that it’s important to get Beta1 out before summer vacation starts, but
we win very little by verifying that we can release the beta of a Qt Multimedia
that’s quite different from the Qt Multimedia we actually want to release.
The FFmpeg provisioning changes are localised to Qt Multimedi
Hi!
I don't have any opinion about FF exception for this but what comes to
https://codereview.qt-project.org/c/qt/qt5/+/561694 I think we can wait
branching & integrate this in 'dev' after it; In big picture it is more
important to keep CI & provisioning as stable as possible this close to fea
Hi!
In my opinion we can wait branching & integrate this in 'dev' after it. And
pick changes in '6.8' after beta1; it is more important to keep CI &
provisioning as stable as possible this close to feature freeze to make sure we
can keep FF schedule (and so on Qt 6.8.0 final schedule as well) a
10 matches
Mail list logo
