# Feature Request

**URL:** <https://www.ruby-forum.com/t/feature-request/234704>\
**Category:** GNU Radio\
**Created:** [March 23, 2015, 5:44pm UTC](https://www.ruby-forum.com/t/feature-request/234704 "2015-03-23T17:44:24Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![addis\_a](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/c4cdca/32.png) [@addis\_a](https://www.ruby-forum.com/u/addis_a)\
**Post date:** [March 23, 2015, 5:44pm UTC](https://www.ruby-forum.com/t/feature-request/234704/1 "2015-03-23T17:44:24Z")

</div>

Hi all,

I wanted to pass a long two features that I wished existed.

I think it would be nice if every block in GRC came with a comment  
field. A  
field for text that does nothing but allow users to add notes to help  
others understand they’re thinking when they set-up the parameters of  
the  
block. It could be thought of as a user definable documentation section.

The second was a ‘comment through’ option. This comments out the block  
and  
passes data through it to the next block. Saves having to mess with  
wires  
between blocks that are commented out.

v/r,  
Rich

---

<div class="post-metadata">

**Author:** ![reback](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/b5ac83/32.png) [@reback](https://www.ruby-forum.com/u/reback)\
**Post date:** [March 23, 2015, 6:31pm UTC](https://www.ruby-forum.com/t/feature-request/234704/2 "2015-03-23T18:31:01Z")

</div>

* * *

Discuss-gnuradio mailing list  
removed\_email\_address@domain.invalid  
[https://lists.gnu.org/mailman/listinfo/discuss-gnuradio](https://lists.gnu.org/mailman/listinfo/discuss-gnuradio)

---

<div class="post-metadata">

**Author:** ![reback](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/b5ac83/32.png) [@reback](https://www.ruby-forum.com/u/reback)\
**Post date:** [March 23, 2015, 7:58pm UTC](https://www.ruby-forum.com/t/feature-request/234704/3 "2015-03-23T19:58:01Z")

</div>

Rich,

GRC has the worst ratio of people committing code (Seth is one of them)  
to importance of the project. There is even an entire wiki page with a  
GRC wishlist:  
[http://gnuradio.org/redmine/projects/gnuradio/wiki/GRCroadmap](http://gnuradio.org/redmine/projects/gnuradio/wiki/GRCroadmap)

…and Sebastian (our main GRC guy) tracks even more stuff on the issue  
tracker. There will be a GRC Working Group call soon. If you (or anyone  
else) would like to contribute, you are very welcome.

Otherwise, GRC feature requests will fall under the bus (besides, it’s  
hard to come up with _new_ requests – most people want the same stuff,  
but no one wants to write it).

If you’re interested, tell us about it, and keep your eyes open for the  
next WG call.

M

---

<div class="post-metadata">

**Author:** ![reback](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/b5ac83/32.png) [@reback](https://www.ruby-forum.com/u/reback)\
**Post date:** [March 24, 2015, 5:57pm UTC](https://www.ruby-forum.com/t/feature-request/234704/4 "2015-03-24T17:57:19Z")

</div>

Sebastian,

Now that the “issue” is on the issue tracker, how long does it usually  
take  
for that to make it into the distributed version of gnu radio? What has  
to  
happen before then? I’m curious.

v/r,  
Rich

On Tue, Mar 24, 2015 at 8:02 AM, Koslowski, Sebastian (CEL) \<

---

<div class="post-metadata">

**Author:** ![reback](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/b5ac83/32.png) [@reback](https://www.ruby-forum.com/u/reback)\
**Post date:** [March 24, 2015, 4:04pm UTC](https://www.ruby-forum.com/t/feature-request/234704/5 "2015-03-24T16:04:10Z")

</div>

On 03/23/2015 05:43 PM, Richard B. wrote:

> The second was a ‘comment through’ option. This comments out the block  
> and passes data through it to the next block. Saves having to mess  
> with wires between blocks that are commented out.

Martin’s quite right, there is way more to be done, than there is time  
=)

In this case, however, I had the code pretty much done already for  
another feature.  
See [http://gnuradio.org/redmine/issues/780](http://gnuradio.org/redmine/issues/780)

Sebastian

---

<div class="post-metadata">

**Author:** ![reback](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/b5ac83/32.png) [@reback](https://www.ruby-forum.com/u/reback)\
**Post date:** [March 24, 2015, 6:02pm UTC](https://www.ruby-forum.com/t/feature-request/234704/6 "2015-03-24T18:02:30Z")

</div>

On Tue, Mar 24, 2015 at 9:55 AM, Richard B. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
wrote:

> Sebastian,
> 
> Now that the “issue” is on the issue tracker, how long does it usually  
> take for that to make it into the distributed version of gnu radio? What  
> has to happen before then? I’m curious.
> 
> v/r,  
> Rich

Rich,

We have two pages that address those questions. Easier than reproducing  
the  
answers here:

[http://gnuradio.org/redmine/projects/gnuradio/wiki/Development#Dealing-with-the-GNU-Radio-Issue-Tracker](http://gnuradio.org/redmine/projects/gnuradio/wiki/Development#Dealing-with-the-GNU-Radio-Issue-Tracker)

and

[http://gnuradio.org/redmine/projects/gnuradio/wiki/Development#How-long-does-it-take-for-my-patch-to-become-part-of-GNU-Radio](http://gnuradio.org/redmine/projects/gnuradio/wiki/Development#How-long-does-it-take-for-my-patch-to-become-part-of-GNU-Radio)

And to add to that last link, also the available time from the developer  
how would be implementing that feature. So it’ll depend on Sebastian  
queuing algorithm.

Tom