Project

General

Profile

Actions

Bug #8287

closed

FT-4XR beep menu options are reversed

Added by Kyle Isom over 3 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
09/29/2020
Due date:
% Done:

100%

Estimated time:
Chirp Version:
daily
Model affected:
Yaesu FT-4XR
Platform:
All
Debug Log:
I read the instructions above:

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

Related to Bug #9247: FT-65E: "5 Beep" is not configured correctlyClosedBernhard Hailer07/29/2021

Actions
Has duplicate Feature #7841: FT-4XE No Beep Setting?ClosedBernhard Hailer04/29/2020

Actions
Actions #1

Updated by Bernhard Hailer over 3 years ago

  • Model affected changed from FT-4XR to Yaesu FT-4XR
Actions #2

Updated by Bernhard Hailer about 3 years ago

  • Status changed from New to Feedback

Kyle, has your patch ever been posted to the developer's mailing list and accepted? Thanks.

Actions #3

Updated by Kyle Isom about 3 years ago

I sent the patch to the dev mailing list and never heard back.

Actions #4

Updated by Rudolph Gutzerhagen about 3 years ago

Sorry, don't see your patch in the developer forum/archive/mailing list. Can you provide a reference?

Actions #5

Updated by Kyle Isom about 3 years ago

I don't have a reference; I sent the email (to chirp_devel@intrepid.danplanet.com) and there was only radio silence.

Actions #6

Updated by Bernhard Hailer about 3 years ago

Ah - chirp_devel@intrepid.danplanet.com is a mailing list. You need to sign up to it before you can post.

Actions #8

Updated by Bernhard Hailer about 3 years ago

Thank you! Please be advised that it may take a while until Dan has time to review and apply the patch.

Actions #9

Updated by Bernhard Hailer about 3 years ago

  • Status changed from Feedback to Resolved
Actions #10

Updated by Bernhard Hailer almost 3 years ago

Kyle, have you ever received any response on your patch?

Actions #11

Updated by Kyle Isom almost 3 years ago

I haven't heard anything back, I assumed it was just taking a while to get to.

Actions #12

Updated by Bernhard Hailer almost 3 years 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!

Actions #13

Updated by Bernhard Hailer over 2 years ago

  • Status changed from Resolved to Closed

This patch never made it into the repository.
We will apply a patch based on ticket #9247.

Actions

Also available in: Atom PDF