discuss-gnuradio
[Top][All Lists]
Advanced

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

Re: [Discuss-gnuradio] A basic but critical problem in beginning of pyt


From: nansai hu
Subject: Re: [Discuss-gnuradio] A basic but critical problem in beginning of python code
Date: Sat, 5 Sep 2009 10:35:16 -0400

So that is the reason for use .run() the gui will display if you py file is modified by a grc file, but if use the .start() function, no gui display even in same program?
 
if it is ture,how can I add some logic after the program started?
I mean if I use start() function ,the code after start() could be executed (use run function these code could not be executed),but the GUI silde or ratiobottom item which add to file by GRC previously could not be displayed?
 
Is there anyway to have both GUI item and some logic after program could be available in same time?

2009/9/5 Josh Blum <address@hidden>
run() is a blocking call.
start() is a non-blocking call.

Also, I believe run() will exit when a block returns -1 in its work method. FYI

-Josh

nansai hu wrote:
When run a python script file, as we know main function will be run first.
We send the class to a object "tb",for instance. Then we have two ways to
let the program run.
One is call tb.run() function,and other is call tb.start() function.Could
somebody told me the difference bewteen these?

In my coding experience, use .run() the gui will display if you py file is
modified by a grc file, but if use the .start() function, no gui display
even in same program.



------------------------------------------------------------------------

_______________________________________________
Discuss-gnuradio mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


reply via email to

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