Hi all guys,
I understand more or less what you are suggesting, although I am not
familiar with any multithreading framework, but at least I could ask
somebody here in the house. The problem is following, as I described in my
other (recent :)) posts:
I have top block which consists of two flowgra
I had a similar problem recently. My solution was to subclass the
flowgraph adding the required functionality. Check out the
_top_block_waiter class in top_block.py. You can reimplement that logic
to e.g. add a time-out the the wait() call on the event or have a
callback executed.
Sebastian
On 0
Hi Nemanja,
typically, clicking your "start" button would spawn a new thread, in
which you top_block.start(), .stop() and .wait(); after wait returns,
you would then use whatever multithreading framework you're using to
notify the threads that need to know.
GNU Radio is not very callback-oriented,
Hi all (again),
is there any way to catch that my flowgraph has finished execution, to
reconfigure it after that and to be able to watch signals in GUI?
In my application I I would like to set some start and end values and to
press some kind of start button. After that flowgraph runs for the firs
