On Tue, Mar 12, 2019 at 11:04 PM Thiago Macieira
wrote:
> No. Catch it before it goes back to Qt code.
>
Roger that!
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
On Tuesday, 12 March 2019 13:58:46 PDT Konstantin Shegunov wrote:
> Noted. My question was more in line with: "Are we getting some kind of a
> replacement or workaround?"
No. Catch it before it goes back to Qt code.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel
On Mon, Mar 11, 2019 at 10:56 PM william.croc...@analog.com <
william.croc...@analog.com> wrote:
> I wrote and installed my own notify function.
>
Yes, thanks, but as far as I understand from the docs this is going away in
the future (or at least it is in threaded code), which is the reason for m
On Monday, 11 March 2019 13:41:11 PDT Konstantin Shegunov wrote:
> Hello,
> Is there a current recommended way of catching exceptions before they
> unwind through the event loop?
Yes: just catch them before letting them come back to any Qt function. You
should treat all your slots and event hand
Hello,
Is there a current recommended way of catching exceptions before they unwind
through the event loop? I want this for "debug purposes" only. I have few
methods that throw and I (think I) catch (all of) my exceptions before they
reach the event loop, but I wanted to be sure I hadn't forgot
Hello,
Is there a current recommended way of catching exceptions before they
unwind through the event loop? I want this for "debug purposes" only. I
have few methods that throw and I (think I) catch (all of) my exceptions
before they reach the event loop, but I wanted to be sure I hadn't
forgotten
