Bug #8287
FT-4XR beep menu options are reversed
Status: | Closed | Start date: | 09/29/2020 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | Kyle Isom | % Done: | 100% |
|
Category: | - | |||
Target version: | chirp-daily | |||
Chirp Version: | daily | Platform: | All | |
Model affected: | Yaesu FT-4XR |
Description
I went to program my FT-4XR with Chirp (it works!), except I found out the beep menu options are reversed. That is, when I selected "OFF", the radio shows as "KEY+SC" and vice-versa.
I have a patch, but I'm opening the bug first as per the dev process.
Related issues
History
Updated by Bernhard Hailer over 1 year ago
- Model affected changed from FT-4XR to Yaesu FT-4XR
Updated by Bernhard Hailer over 1 year ago
- Status changed from New to Feedback
Kyle, has your patch ever been posted to the developer's mailing list and accepted? Thanks.
Updated by Kyle Isom over 1 year ago
I sent the patch to the dev mailing list and never heard back.
Updated by Rudolph Gutzerhagen over 1 year ago
Sorry, don't see your patch in the developer forum/archive/mailing list. Can you provide a reference?
Updated by Kyle Isom over 1 year ago
I don't have a reference; I sent the email (to chirp_devel@intrepid.danplanet.com) and there was only radio silence.
Updated by Bernhard Hailer over 1 year ago
Ah - chirp_devel@intrepid.danplanet.com is a mailing list. You need to sign up to it before you can post.
Updated by Kyle Isom over 1 year ago
I've signed up and resent my patch (http://intrepid.danplanet.com/pipermail/chirp_devel/2021-January/006294.html).
Updated by Bernhard Hailer over 1 year ago
Thank you! Please be advised that it may take a while until Dan has time to review and apply the patch.
Updated by Bernhard Hailer over 1 year ago
- Status changed from Feedback to Resolved
Updated by Bernhard Hailer over 1 year ago
Kyle, have you ever received any response on your patch?
Updated by Kyle Isom over 1 year ago
I haven't heard anything back, I assumed it was just taking a while to get to.
Updated by Bernhard Hailer over 1 year ago
Hmm. I checked the developer's mailing list, and your patch is there. There were some builds made since; so it may make sense to ask whether it has been overlooked. Good luck!
Updated by Bernhard Hailer 11 months ago
- Status changed from Resolved to Closed
This patch never made it into the repository.
We will apply a patch based on ticket #9247.