[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss-gnuradio] GRC - python code generation quirk for Function Probe
From: |
Darren Long |
Subject: |
[Discuss-gnuradio] GRC - python code generation quirk for Function Probe with empty BlockID |
Date: |
Fri, 25 Apr 2014 17:45:01 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 |
Hi,
I've been pottering around in GRC trying to get a pair of function
probe's to update the QT fosphor GUI sink's centre frequency by calling
self.set_freq(float(subprocess.check_output(['/usr/bin/rigctl', '-m',
'2', 'f']).strip()))
at 5Hz and
self.set_samp_rate(self.samp_rate)
at 20Hz.
This seems to work, except for the fact that the GRC python generator
generates the following lines of code instead of that I've shown above:
val = self..set_freq(float(subprocess.check_output(['/usr/bin/rigctl',
'-m', '2', 'f']).strip()))
and
val = self..set_samp_rate(self.samp_rate)
Note the pair of dots in those lines. This occurs because the Block ID
in the function probe is empty, in that I want the block ID to refer to
the top block, i.e. self. I can't put "self" as the Block ID, as the
generated code is "self.self" which Python moans about. leaving the
BlockID empty creates the pair of dots.
I wonder if GRC could/should be modified to suppress the extra generated
dot if the Block ID is empty? It would certainly help me to avoid
editing generated code :)
Cheers,
Darren, G0HWW
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Discuss-gnuradio] GRC - python code generation quirk for Function Probe with empty BlockID,
Darren Long <=