I am creating a hardware source block and ran into an issue where the
destructor for the block does not appear to get called when closing the
flowgraph. This is problematic because I'm using the destructor to release
hardware resources. I finally discovered that the problem only exists when
using t
I am creating a hardware source block and ran into an issue where the
destructor for the block does not appear to get called when closing the
flowgraph. This is problematic because I'm using the destructor to release
hardware resources. I finally discovered that the problem only exists when
using t
I'm using the gr-modtool that is now included with gnuradio to add a block
to an existing module that was created with an earlier version of
gr-modtool.py. The swig.i file originally looks like:
%include "gnuradio.i"
%include "testmod_swig_doc.i"
{
#include "testmod_testblock.h"
}
GR_SWIG_BLOCK_
On Wed, Feb 13, 2013 at 4:44 PM, Tom Rondeau wrote:
> On Wed, Feb 13, 2013 at 4:10 PM, Eric B wrote:
>
>> I'm using the gr-modtool that is now included with gnuradio to add a
>> block to an existing module that was created with an earlier version of
>> gr-modtool.p
>So I think its sort of fundamental the the message ports cant be scaled
>like that because they are named and not linearly indexed. You could
>find a way do to it, but its a more invasive GRC change I guess. Perhaps
>Martin's GSoC student might consider doing this for the GRC
>improvements, if not
