On 14.10.2015 00:08, Marius Cachelin wrote:
> Hi,
>
> You were right, when I click the cross button to close the window, all
> my new objects are deleted, even if my destructor is not called.
>
> I tried to not using Qt GUI, and instead, using no GUI, but it is the
> same behavior.
>
> Actually,
Hi,
You were right, when I click the cross button to close the window, all my
new objects are deleted, even if my destructor is not called.
I tried to not using Qt GUI, and instead, using no GUI, but it is the same
behavior.
Actually, during the runtime, my application records some information (
Hi,
> Actually, I don't mean the red cross in GRC. My application is run in QT GUI
> mode.
> So, is the cross on the top of my window a stop button?
Yes, it should stop the flow graph cleanly.
However since everything uses smart pointers, it won't "delete" the
object at that point and I'm not
Hi Sylvain,
Thanks for your reply.
Actually, I don't mean the red cross in GRC. My application is run in QT
GUI mode.
So, is the cross on the top of my window a stop button?
Thanks.
2015-10-13 9:28 GMT+02:00 Sylvain Munaut <246...@gmail.com>:
> Hi,
>
> > When I click on the cross symbol to ex
Hi,
> When I click on the cross symbol to exit my application, the destructor of
> my block is never called.
If you mean the red cross in GRC, then this is a "KILL" button, not a
stop button. The process is forcibly terminated and destructors won't
be run.
Cheers,
Sylvain
Marius,
what happens if the fg terminates itself (e.g. add a head block)?
M
On 09.10.2015 02:08, Marius Cachelin wrote:
> Hi everyone,
>
> I am writing here concerning the destructor of a new block.
>
> I want to print out some information recorded during runtime ( # packet
> sent, # packet re
Hi everyone,
I am writing here concerning the destructor of a new block.
I want to print out some information recorded during runtime ( # packet
sent, # packet received... and so). So, I set "std::cout..." statement
inside the destructor of my block, following these 2 tutorials :
http://gnuradio
