discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] GRC questions


From: Josh Blum
Subject: Re: [Discuss-gnuradio] GRC questions
Date: Thu, 21 Apr 2011 09:50:52 -0700
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110223 Lightning/1.0b2 Thunderbird/3.1.8


On 04/21/2011 09:19 AM, Tom Rondeau wrote:
> Josh,
> 
> Two issues in GNU Radio companion.
> 
> I'm working on a hier_block in GRC and want it to have multiple outputs.
> When I generate the block, though, I get a few problems. First, only one
> output pad is exposed. Looking at the generated XML file, I see that only
> one source block is being created (I have four pad sinks). When I look at
> the Python file, the io signature for the output is correct, but any calls
> to the output are all (self,0), so there seems to be no distinction of what
> pad sink is being used.
> 
> When I hand-edited the files to what they should be, the block works fine in
> GRC.
> 
> Is this a bug or am I doing something wrong?
> 

Thats a long-standing bug thats been around since the vector of
io_signatures was added. I guess I will fix it this time before I get
too distracted.

> Also, when I double-click on a QtGui sink, I get this message in my console:
> 
> Traceback (most recent call last):
>   File "/usr/local/lib/python2.6/dist-packages/gnuradio/grc/gui/Param.py",
> line 56, in _update_gui
>     Utils.parse_template(TIP_MARKUP_TMPL, param=self.param).strip(),
>   File "/usr/local/lib/python2.6/dist-packages/gnuradio/grc/gui/Utils.py",
> line 89, in parse_template
>     return str(Template(tmpl_str, kwargs))
>   File "/usr/lib/pymodules/python2.6/Cheetah/Template.py", line 981, in
> __str__
>     def __str__(self): return getattr(self, mainMethName)()
>   File "cheetah_DynamicallyCompiledCheetahTemplate_1303402270_04_59718.py",
> line 131, in respond
>   File "cheetah_DynamicallyCompiledCheetahTemplate_1303402270_04_59718.py",
> line 88, in truncate
> TypeError: <lambda>() takes exactly 1 argument (0 given)
> 
> 

I have seen that too. Its been innocuous enough to ignore, so i have
never looked into the cause.

-Josh



reply via email to

[Prev in Thread] Current Thread [Next in Thread]