[chirp_devel] [h777] Fix some settings not taking effect on Baofeng 888 and variants

[Dan Smith]

> I have another datapoint, external to CHIRP and Radioddity. miklor.com has 2 software versions listed that can program the BF-888 class radio. 
> One version is listed as "BF-888S v1.05" and the other is listed as "ZT-V68 2007"
> 
> - The "v1.05" software writes the data blocks in the same order as CHIRP, also using only the "W" commands.
> - The "ZT-V68" software, writes the data blocks in a different order than CHIRP (as reflected by my patch) and uses a "Y" command for those middle blocks.
> 
> I found through testing that:
> - The "Y" command is not strictly necessary. 
> - Using all "W" commands works, as long as the order (_ranges variable in h777.py) is updated (as seen in my patch).
> - Using the "Y" commands with the original order (unmodified _ranges variable) does not work.

Okay, so your suggestion is now to just change the ranges and not use the different command at all, correct?

>> Hmm, I've set several of these on my BF-888 clones and not had a problem. As such I'm a little reluctant to apply this, being concerned that maybe we have a variant out there and that applying this
>> to fix half of them will break the others.
> Agreed. I would love to get more feedback. I've tested the changes on my older Baofeng 777S radios but my "collection" is quite small.

Well, my collection isn't that large, but it turns out I'm a bit full of it anyway. In testing, I realized I too am unable to turn off the little chinese lady in my clones with the driver as it is in-tree, but can with your patch (which seems to work fine). Mine are only a couple years old at the most. I'm still worried about breaking older models, mind you, but I don't see to have any of those.

> This is where your intuition is much much greater than mine. 

Well, my intuition tells me that, if anything, the command should matter and the order of the ranges should not (or at least doing them in non-sequential order would not be better). So... :)

>> why you think it matters?
> It's still an issue, someone posted yesterday about 888 settings not sticking. https://chirp.danplanet.com/issues/6997

I meant why you think the range order matters, not why you think we should fix bugs, but...thanks :D

So, answer my question above about trimming the patch to just the ranges so we can proceed. If that's what you suggest, please send an updated patch and I will test (again) and apply.

Thanks!

--Dan