Re: [Discuss-gnuradio] "Catching" end of flowgraph execution with GUI

2015-05-06 Thread Nemanja Savic
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

Re: [Discuss-gnuradio] "Catching" end of flowgraph execution with GUI

2015-05-05 Thread Koslowski, Sebastian (CEL)
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

Re: [Discuss-gnuradio] "Catching" end of flowgraph execution with GUI

2015-05-05 Thread Marcus Müller
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,