Please remember to keep replies in the various Announcement threads specific to that Release or Release Candidate. Discussion about other feature requests that weren’t included in a specific release need to go elsewhere – which is why I moved this discussion to it’s own thread. Though really, discussions about a specific feature request, like the issue #14269 you linked to, will probably get more response from a developer if the conversation is kept in that issue, rather than trying to pester him in an inappropriate location (like the release candidate announcement).

Fortunately, @Alan-Kilborn made a reply in the issue, and the original poster has chimed in again with more details, so that’s good. (I am guessing that user is you – it’s a very different username, but as one who is @PeterJones here and pryrt in GitHub, I can definitely understand having a different username in different websites)

I personally think the original request was a reasonable one, and I’m a bit confused why the developer thought he’d already addressed it, when it obviously hadn’t changed since October of last year… I think he’s been trying to close out a lot of older issues recently, and he’s not being very detail-oriented (or otherwise getting confused) when giving his comment-while-closing. Hopefully he’ll re-open the issue for you. Good luck.