Marcus Müller

TODO: Convert me to issue against GRC-QT,

@minhaj6 no. Unless an issue is closed or you have clear indication we forgot to close it, you'll have to assume it's still open for a reason ;)

> I think I figured it out: GRC does the import only once, and whatever was defined at that time is assumed to be there forever. Nope, that's the Python...

Still reproduces. Small script to test this (we could upstream that as unit test once gr_modtool can create blocks without QA without manual interaction) included: https://gist.github.com/marcusmueller/f03ff708e0975c82dc80c06156c1ae3b

I don't even have a ctrlport build at the moment, definitely warranting a dedicated look into the state of ctrlport + perf monitor

> The wiki could use some guidance on how to use, and where in the flowgraph to put, the throttle to get the desired effect. Guessing that it often goes...

@willcode Looks like this now:   

I also added the `deprecated` flag to the "old" throttle – since we have no mechanism to automatically upgrade to the new one, and the new YAML will cause old...

Yeah, that's why I made the deprecation a separate commit – no need to deprecate it now, so if backporting, simply omit that commit.

Re: auto setting: that's what happens when you leave it at 0 – no limited block duration. Or do you mean it should default to something like 0.1 s?