Re: [Discuss-gnuradio] How does a C++ custom block kill the FlowGraph

2014-02-22 Thread Martin Braun
On 02/21/2014 06:27 PM, Tommy Tracy II wrote: Both sub-flowgraphs use the same top block (you can’t have two top blocks in one application). Unfortunately, because they are disjoint, if the 1st Source returns WORK_DONE, it won’t call the other blocks’ destructors as I would expect. It appears

Re: [Discuss-gnuradio] How does a C++ custom block kill the FlowGraph

2014-02-21 Thread Tommy Tracy II
Thank you. I have another question. I have a strange situation where I have two sub-flowgraphs. The two sub-flowgraphs are connected by a message queue. The 1st Sink can talk to the 2nd Source through this queue. TOP BLOCK{ 1st subgraph [1st Source]——[…]——[1st Sink] 2nd subgraph

[Discuss-gnuradio] How does a C++ custom block kill the FlowGraph

2014-02-10 Thread Tommy Tracy II
Dear Gnuradio Community, I have some custom gnu radio blocks that make up my flow graph. I want one of my blocks to kill this flow graph (cause all blocks to call their destructors). When the source is computing its last set of inputs, I want it to let all the other blocks know it’s