Thanks, I updated to pull in all of the latest changes and the pad
source/sink now have the wildcard option as you suggested. So I tried
to create a simple hierarchical block that has one message input and
one message output using wildcard pads. Everything works great with
generating the block in companion and importing it into another
flowgraph, but when I try to run it, I'm getting the error below. Any
ideas?
Traceback (most recent call last):
File "/root/mockup_test.py", line 118, in <module>
tb = mockup_test()
File "/root/mockup_test.py", line 47, in __init__
self.gui_wrapper_0 = gui_wrapper()
File "/root/.grc_gnuradio/gui_wrapper.py", line 16, in __init__
gr.io_signature(1, 1, 0*1),
File
"/usr/lib64/python2.6/site-packages/gnuradio/gr/gnuradio_core_runtime.py",
line 217, in io_signature
return _gnuradio_core_runtime.io_signature(*args, **kwargs)
RuntimeError: gr_io_signature(3)
Thanks,
Roy
On Tue, Nov 20, 2012 at 2:00 PM, Josh Blum <j...@ettus.com> wrote:
>
>
> On 11/20/2012 08:08 AM, Roy Thompson wrote:
>> Is it possible to create hierarchical blocks that have GrExtras
>> messages as the inputs or outputs? The standard pad source and sink
>> blocks don't appear to provide a way to do this.
>
> Not sure if this is in a release yet, but the pad source/sink have a
> wildcard option for the port IO type. You can use this.
>
> -josh
>
>>
>> Thanks,
>> Roy
>>
>> _______________________________________________
>> Discuss-gnuradio mailing list
>> Discuss-gnuradio@gnu.org
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>
>
> _______________________________________________
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
