Huh, I'm out of my depth here.
However, yes, every subclass of gr::block automatically has a
pmt::mp("system") message port, that you can use to do such things.
Best regards,
Marcus
On 02.09.2015 14:47, Nemanja Savic wrote:
> Namely,
>
> my workless function block blocks my flowgraph when I call
Namely,
my workless function block blocks my flowgraph when I call unlock(). I made
a method where I set d_finished to True, but this doesn't help.
Nemanja
On Wed, Sep 2, 2015 at 2:16 PM, Nemanja Savic wrote:
> Hello again,
>
> could you please Marcus, or somebody else, give me some hint for s
Hello again,
could you please Marcus, or somebody else, give me some hint for sending
done message to a block's "system" port. Are all blocks by default
subscribed to system port?
Best,
Nemanja
On Tue, May 26, 2015 at 2:37 PM, Nemanja Savic wrote:
> Hi,
>
> thank you Marcus for your fast answe
Hi,
thank you Marcus for your fast answer. Well, the problem is that nobody
ecept scheduler knows when the flowgraph has finished, so I don't know who
should sent that message to the block. This is however not of crucial
importance for me. Namely I wanted to test some of my custom blocks, and
test
Hi Nemanja,
the point is that with message passing, it's not clear that your block
is ever finished.
Hence in block.cc, we have a mechanism to retrieve the "finishedness" of
a pure-message-block.
bool
block::finished()
{
if((detail()->ninputs() != 0) || (detail()->noutputs() != 0))
Hi all,
I have a block that is used only for acepting messages and writing their
content into database. The block is written in python and it has no work
function, but only constructor and message handler. However when I run my
flowgraph it won't finish until I terminate it. When I exclude this bl
