Bug #8287

FT-4XR beep menu options are reversed

Added by Kyle Isom 12 months ago. Updated about 1 month ago.

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

related to Bug #9247: FT-65E: "5 Beep" is not configured correctly Closed 07/29/2021
duplicated by Feature #7841: FT-4XE No Beep Setting? Closed 04/29/2020

History

#1
Updated by Bernhard Hailer 12 months ago

  • Model affected changed from FT-4XR to Yaesu FT-4XR

#2
Updated by Bernhard Hailer 8 months ago

  • Status changed from New to Feedback

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

#3
Updated by Kyle Isom 8 months ago

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

#4
Updated by Rudolph Gutzerhagen 8 months ago

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

#5
Updated by Kyle Isom 8 months ago

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

#6
Updated by Bernhard Hailer 8 months ago

Ah - is a mailing list. You need to sign up to it before you can post.

#8
Updated by Bernhard Hailer 8 months ago

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

#9
Updated by Bernhard Hailer 8 months ago

  • Status changed from Feedback to Resolved

#10
Updated by Bernhard Hailer 6 months ago

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

#11
Updated by Kyle Isom 6 months ago

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

#12
Updated by Bernhard Hailer 6 months 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!

#13
Updated by Bernhard Hailer about 1 month ago

  • Status changed from Resolved to Closed

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

Also available in: Atom PDF