Declan, is there any way I could get you to try to keep all this yaesu-special-banks stuff mostly to a single thread on here? My mailer (like many modern ones) groups things by conversation for context, but I have a bunch of conversations about this topic now. Not a huge deal, but I'd sure appreciate a little more grouping :)
It works with the Yaesu presets, which fit just fine into the ft1d.py driver. Thank you for your help.
Cool.
It’s not quite ready for prime time; I do have a UI issue.
In the Banks tab, regular memories are selected and stored correctly. These special memories are stored correctly, but they must be selected by pressing on the check-box on the second row UNDER the one I want. It seems to be consistent about that for all bankable specials. Add_memory_to_mapping seems to receive a memory number two too low.
That almost definitely means you're not being consistent in your numbering of the specials between get, set, and features. If you try with the "Fake Clone" fixture I put into that set, you'll see that bank selections are correlated to where you click properly.
Maybe this is all moot, anyway. My immutable Yaesu preset specials show up in the memory list, and I can copy them out into regular memories, which folks can select in the bank as normal.
But that's not the goal or solution here right? The goal is to allow the presets to be banked without duplicating them in the regular memory right? The latter seems to totally defeat the point (and all the extra work) of implementing this in that way.
Is there any way to convince python to ignore a multiple-inheritance class like SpecialBankModelInterface if it doesn’t exist (such as in the present mainline.) The code would work in the way just mentioned, and the little bit of extra coding would never get called.
Wait, what? I'm not sure what you're asking.
--Dan