[Top][All Lists]

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

Re: [Discuss-gnuradio] Enable/Disable Processing on QT Tab Page Selectio

From: Nigel Steed (XENINT)
Subject: Re: [Discuss-gnuradio] Enable/Disable Processing on QT Tab Page Selection
Date: Wed, 15 Feb 2017 16:05:56 +0000

Thanks Derek,


I never spotted the COPY block.


Kind regards,





From: Derek Kozel [mailto:address@hidden
Sent: Tuesday, February 14, 2017 9:37 PM
To: Nigel Steed (XENINT) <address@hidden>
Cc: address@hidden
Subject: Re: [Discuss-gnuradio] Enable/Disable Processing on QT Tab Page Selection


Hello Nigel,

The Copy block is a useful block for enabling/disabling portions of flowgraphs. I think you will need a custom python module (which can be included in GRC) to do the tab detection. I think having the ability to register functions onto the currentChanged signal or similar would be a useful addition to the qtgui Tab Widget.






On Tue, Feb 14, 2017 at 7:27 AM, Nigel Steed (XENINT) <address@hidden> wrote:

Hi All,


I have prepared a GRC Flowgraph with several tab pages using the QT Tab Widget. Each tab page has different displays such as spectrograms, waterfalls etc.


Behind these tab screens I have separate processing blocks running to generate the data to display, all in parallel.


I am wondering if there is a neat way to only enable processing blocks when the corresponding tab is active ?


My first attempt at this was to use a number of throttle blocks located in different signal paths associated for each tab, and dynamically set the sample rate to 0 when the tab is not active to disable data flow – but this module seems to cause the entire flowgraph to stop.


My next approach is to generate an OOT Module to enable/disable data flow unless anyone knows of a neater way ?


Is it possible to detect what tab is selected from within GRC ?


Any comments much appreciated.



Discuss-gnuradio mailing list


reply via email to

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