On Tuesday, 9 May 2023 17:33:04 PDT Alexander Dyagilev wrote:
> The most ugly thing coming from it is that it changes the way app works.
> It executes additional event loop in those regions of code where it's
> not supposed to happen. This can bring additional bugs and/or change an
> apps' behavior
Yes, it's a horrible dialogue and it must be eliminated once and forever.
The most ugly thing coming from it is that it changes the way app works.
It executes additional event loop in those regions of code where it's
not supposed to happen. This can bring additional bugs and/or change an
apps'
I will use the ignore when I expect the assertion failure but want to continue.
Usually when the assertion was added because something strange happened, and
Im trying to find what assumption in the function stack was broken.
-Original Message-
From: Interest On Behalf Of Thiago Macie
Hello,
I've just found a very disappointing issue: queued connections does NOT
work with objects from shared libraries under iOS...
I'm trying to port my existing application to iOS and it seems it would
be impossible because of this...
I've created bug report: https://bugreports.qt.io/brow
On Monday, 8 May 2023 16:50:51 PDT Scott Bloom wrote:
> I do on a regular basis. Not sure why you say it’s a horrible dialog, it’s a
> message box 😊 with the assertion information.
Because it's "Abort", "Retry", "Ignore" that tells you that "Retry will launch
the debugger", so it doesn't actually
