[chirp_devel] [PATCH 1 of 2] [px777] fix no-tone identifier. Fixes #363

[Tom Hayward]

On Mon, Dec 17, 2012 at 4:52 PM, Dan Smith <dsmith at danplanet.com> wrote:
> Thanks!
>
>> # HG changeset patch
>> # User Tom Hayward <tom at tomh.us>
>> # Date 1355706045 28800
>> # Node ID 2fe6ec6bf7bc5add754476e9dfd4eea5aec6d5da
>> # Parent  49c2ca133e8652aa17cdf8d79ce3717009803892
>> [px777] fix no-tone identifier. Fixes #363
>
> This one doesn't pass the tests...

I'm not really sure how to make this one pass the tests. It appears
there are two values the radio interprets as no-tone, 0x00 and 0xff.
Channels programmed for no-tone with the Puxing software will have the
value 0xff. Channels programmed for no-tone from the PX-777 front
panel will have the value 0x00. When reading the radio, Chirp breaks
when it encounters the 0x00 value. Hence my patch. When Chirp
writes/copies a new channel, it sets the tone value to 0xff, just like
the Puxing software. This means a copy operation changes 0x00 to 0xff.
The radio doesn't care, but this breaks the Chirp tests.

Tom KD7LXL