>> However, someone who is using currently exceptions, they will have to
change
their code for more complicated code because we decided to forbid it ("for
their own good")
>> May I recall that exceptions through signals and slots always worked,
and was
used.
It never worked.with other than direct
Assuming exceptions are enabled for signal/slots what is going to happen
with Qt::QueuedConnection?
As far as I understand at this point you can't catch exception in the
signal.
That means you will have to do it in the event loop. What is going to
happen next? Re-throw it and an uncaught exception
Great ! Thanks!
Did not see this announcement on interest, so forwarding message there.
Alex
On Thu, Apr 11, 2013 at 3:57 AM, Turunen Tuukka wrote:
>
> Hi All,
>
> Visual Studio Add-In 1.2.1 for Qt 5 is now released, see:
> http://blog.qt.digia.com/blog/2013/04/11/visual-studio-add-in-1-2-1-
>> Why that's my favorite tool for detecting memory leaks of windows.. if the
>> numbers keep growing you have a problem.
It does not detect leaks. It reports memory claimed by process.
So its usage is limited.
It is not useless, but you can't base memory leaks claims on the
information it provid
