drslebedev

Thank you very much for your feedback. I would like to clarify an important point concerning the length of code lines. Our goal is not to deliberately write long lines...

The handling of this edge case isn’t really discussed. Generally, this is a rare edge case, particularly in the case of `uint64_t`. One possible solution could be to address this...

If at least one `Async` output port is present, `processBulk` is always called, even if no input samples are available (unless Async output port constraints are not met, namely min/max...

In general, these three cases behave similarly, but there are some differences to note. The main differences between these cases lie in how constraints are applied: - **Sync Ports**: Both...

For the output `Sync` port, the `processBulk` function is only invoked when input samples are available. Otherwise, it's unclear how many samples to provide for the `Sync` output port, as...

Hi @dantti , most of the issues are already implemented and merged. The only missing part is adding stored settings via Message port. But you can start working on UI.

Thank you very much for your commit! Is there anything else you need from our side to complete the issue and submit a PR?

We propose extending the Message API to support updated `CtxSettings` with the following functionalities: - Get settings for a specific context - Set settings for a specific context - Activate...

See follow-up issue https://github.com/fair-acc/gnuradio4/issues/452