That seems to work, I didn't realize that grc would allow connecting a
message port to a byte port.
Thanks for your help.
-Roy
On Wed, Nov 21, 2012 at 3:21 AM, Josh Blum wrote:
>
>
> On 11/20/2012 02:13 PM, Roy Thompson wrote:
>> Thanks, I updated to pull in all of the latest changes and the pa
On 11/20/2012 02:13 PM, Roy Thompson wrote:
> 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
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
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 ha
Trying using 'bytes' as the data type for the pad source/sinks. This
seemed to work for me.
-John
On Tue, Nov 20, 2012 at 8: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
> bloc
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.
Thanks,
Roy
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
