On 11/14/2019 11:52 AM, Glen I Langston wrote:
Hi Amr,
Thanks for your suggestion.
However when I select no-gui, then all the QT blocks go RED in my designs in
gnuradio-companion.
I was hoping that they would instead just go quiet and use the default values.
I can, of course, just delete all the QT blocks, but then when going back
to debugging/improving I’d have to put them back in.
My hope is not yet implemented, it appears.
Best regards,
Glen
There is a "disable" function in GRC -- so the scaffolding for the block
is there, but not actually enabled in code generation.
Unfortunately, there's no GRC-way to do this at runtime.
On Nov 14, 2019, at 9:53 AM, Amr Bekhit <amrbek...@gmail.com> wrote:
Hi Glen,
In the top right corner of the flow you will see the flow properties box. In
there you can disable the GUI. You can then run your python file directly, or
even call the created class object from another file (have a look inside the
main function to see how the flow is instantiated). You can also get and set
variable values in runtime via Python and have the flow update, just like you
can with the GUI.
On 14 Nov 2019 Thu at 5:28 PM Glen I Langston <glen.i.langs...@gmail.com> wrote:
This email is a question concerning the Gnuradio transition from
a GUI interface to purely python execution.
We’ve developed a series of gnuradio-companion compatible designs
that are "just about" perfected from our point of view. Now we’re going
from interactive mode to fully automatic startup and execution from
computer reboot.
Our designs now immediately start capturing radio astronomy spectra
and transient events.
Is there a simple mechanism to turn off and on the GUI interface? Maybe
just in the control block?
Sorry if this is an obvious question.
Thanks - Glen
