I'd categorize this somewhere between feature request and bug report.
Could you raise this as an issue on github.com/gnuradio/gnuradio/issues
, please?
Generally, tracking could be possible, but is rather complicated,
because we have different namespaces in which parts of the flow graph
On Mon, Aug 31, 2020 at 8:11 AM Jeff Long wrote:
> Since there is no way of knowing what global names will conflict in the
> future, it could be useful for GRC to prefix ids (id_audio), make them part
> of another structure (ids.audio), or something similar. This adds
> complexity to manual
Since there is no way of knowing what global names will conflict in the
future, it could be useful for GRC to prefix ids (id_audio), make them part
of another structure (ids.audio), or something similar. This adds
complexity to manual coding in Python, so it's a tradeoff.
On Mon, Aug 31, 2020 at
Hi
One of my flowgraph was generating the error:
self.audio_sink_0 = audio.sink(audio_rate, '', True)
AttributeError: 'int' object has no attribute 'sink'
This error was not easy to debug since the error message sounds like
there was a library error (which was not the case here).
My
