I’ve a suggested change to the FT-1D/FT2D driver to support the Yaesu WIRES-X settings that the radios handle. I don’t yet like the partial implementation, so I ask for suggestions.

The FT2D can define five named categories of up to 20 digital rooms each. There’s a new settings tab for WIRES-X, which will presently list the following (I intend to make them modifiable inside CHIRP, if I can figure that out. Those changes don’t work yet. Are there ANY instructions for getting the callback to work correctly for changing?)

Here’s a synopsis of what the settings menu provides now: Category1 <text name1> Room ID1 <string of digits> Room Name1 <string> Room ID2 <string of digits> … Room ID20 <string of digits> Room Name20 <string> Category2 <text name 2> Room ID1 <string> … Room Name20 <string> Category3 < …. Category4 <… Category5 <…. … Room Name20 <string>

I really don’t like multiple aspects: - ID and Name are on separate lines… I think it’d be better if they were each on one line, possibly indented from the Category name entries. - It’s distracting to always have the category names separated by 40 lines, many of which are blank (although they need to eventually be accessible for editing). Is there a way to have a pull-down for rooms, so they’re not shown ’til wanted to see or change? I suppose it’d not be unreasonable to only display the first blank entry in a series of blanks. - Again: modifications to the values don’t yet work.

I attach my diff text file, wherein I define a Wires-X settings memory structure, a callback routine (it errors and it doesn’t work) and a settings subroutine. They’re REALLY, really not ready for formal inclusion. I’ll be continuing with my trial-and-error misprogramming. I REALLY would like some feedback on this, please.

Clearly, I’ve got an image with Wires-X data in it to test it against, but you can see some of causes my discomfort with the test FT-1D or FT2D images.