I’ve been in software development a good many years. Since before Microsoft DOS, in fact. (Yes, Virginia, once-upon-a-time there was no Microsoft Windows.) I’ve designed and written software both as a paid professional and as a hobbyist–on and for a wide variety of platforms and in everything from machine code to 4GL languages.
It has been my experience that attempting to satisfy every enhancement request under the sun results in a product that only people with advanced engineering degrees can use, and still you’ll get more requests for additional bells and whistles.
It is not my intention to discount the value of Tallmomof2’s request, but only to say that each and every request has to be weighed as to its complexity–both the complexity of engineering, which directly affects product stability, and end-user use complexity, which affects usability–against to the number of users requesting it. At the extremes: Few requests and high complexity: Probably not. Many requests and low complexity: Probably so.
I’ve a simple project you’ll find on Linux distros. I’ve received many, many requests over the years to add this or that or the other feature. I’ve rejected most of them, as per my evaluation criteria above. Even when somebody else did all the work and submitted a patch. The result is it’s stable and people use it. Somebody once forked the project and tried to add every bell and whistle under the sun. After much initial excitement it was gone, had disappeared, in less than a year. Nobody could use it.
Oft times simple is better, even if it doesn’t do everything you’d like it to do.