Hi Eugene,
ouch, that's a heavy bug, considering we have blocks called agc2 in-tree.
Thanks for reporting this! Do you want to create an issue on
https://github.com/gnuradio/gnuradio/issues , or would you prefer we do
that? (I'd of course personally prefer you'd, as the discoverer &
solver, at le
We figured out the cause of this error. I had a block called 'vector_sink2' .
I also have blocks called vector_sink. Turns out the block naming simply
appends the block's index to it.
The first vector_sink2 gets called vector_sink21
The first vector_sink gets called vector_sink1
So at some po
Hi Eugene,
uh-oh. The Global Block Registry is definitely not one of the most
modern parts of GNU Radio; personally, I'd argue, it shouldn't exist,
but meh, GNU Radio is a naturally grown project, so we need to rely on
it. Plus I haven't found the time to get rid of it (but neither have I
found go
I have a rather complicated GR application. I create (Python, w/out grc)
multiple top_blocks, each containing dozens of blocks. To make things even
more complicated, the flowgraphs are created in stages - using runtime
reconfiguration to add more blocks.
Everything works fine until I reach so
