Background: The Yaesu FT1D and FT2D are able to define and use special memory locations and also define some preset special memories that are not part of the memory image.

These radios can reference the locations in the memory banks. IF THE RADIO DEFINES SUCH BANK, then CHIRP WILL FAIL to access that bank forevermore, until the radio manually deletes the association

I’m on my way to managing the special memories in the FT1D driver. I’ve already added basic access to the FT1D’s scan-limit registers. I found that other Yaesu drivers seem to have similar functionality already.

Problem:

The only way I can imagine to permanently fix the problem is to enable special memory access in bankedit.py. I envision having a button similar to the memedit.py “Show Special” button, which will increase the number of memory locations that are shown in the Bank tab.

I’m woefully ignorant of the python -> gtk and chirp/ui -> python activity. I find the memedit.py and bankedit.py structures to be so dissimilar that it’s difficult to simply copy’n’paste. So in the handholding department, PLEASE:

Questions:

- How to add functional buttons to bankedit.py?

- How to effect displaying more memory locations in the bankedit.py when the button is selected? The present matrix display seems OK, I’d just like to add (many) more active rows. 

— Because of the multitude of memories available, it’d be nice to also remove empty entries among the rows (meaning that “show empty” toggle would also be desirable.)

- The display will also need to be active, so both ‘get’ and ‘set’ functionality will be needed.

Declan Rieb WD5EQY