A “broken” image from my FT2D. Bank 24 has entries from the immutable fixed special locations, one from each of weather, marine VHF and SW broadcast. I entered them manually into the radio.

Okay, just now getting around to looking at this. It would really help if you could be more descriptive with your reporting of this stuff, as it’s really difficult for me to follow. I haven’t looked at this code in a really long time, don’t really use any Yaesu radios (with their weird bank system) and definitely not any of the newer ones.

IIRC, I was going to use this broken image to reproduce the behavior you describe, which is that once you’ve touched a bad bank (with immutable memories in it), then the UI is unable to make any other changes.

Loading your image, I can’t really tell which affected bank or memory I should use to reproduce the issue. Trying to add memory 1 to bank 4 yields the “index out of range” error. Then trying to add memory 2 to bank 5 gives me the same. In fact, adding any memory to any bank seems to yield the same result. The UI never seems to get stuck, which I think is what you said was happening, and which I said would be a big problem.

So, can you try to again describe, with specific actions what I need to do to reproduce the issue that affects just the banks with immutable memories (or whatever it is)? Specifically “open the memory, go to banks tab, click check box on memory X for bank Y”, etc.

Thanks,

—Dan