It looks as though it may have been addressed but never actually added in?

http://chirp.danplanet.com/attachments/513/fix_kenwood.patch

On Wed, Apr 8, 2015 at 12:39 PM, Tom Hayward tom@tomh.us wrote:

On Wed, Apr 8, 2015 at 4:55 AM, Ryan Tourge ryan.tourge@gmail.com wrote:

...

I made some changes to kenwood_live.py on my local system (mac) to allow CHIRP to work with all the frequency steps the Kenwood 271/281/471

supports

...

(2.5 Khz was what I was interested in). It works great on my mac and

linux

...

machines. For it to work on windows I would need to recompile from source correct?

This is the use case the Load Module feature was designed to solve. To use it, turn on developer features, then go to File > Load Module, and choose your edited kenwood_live.py file every time you launch Chirp.

The optimal long-term solution is to submit these changes for inclusion in Chirp, so that everyone can benefit from your work.

Tom KD7LXL _______________________________________________ chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers

...

http://chirp.danplanet.com/attachments/513/fix_kenwood.patch

I wouldn't be surprised if no one ever noticed it there, or if the author even intended it to be merged into Chirp.

Indeed.

Also, testing something like that on multiple platforms is generally not required because of how chirp works. Most of us don't test our code on multiple platforms, save the occasional UI patch.

If that patch works and someone submits it to the list as a proper patch, we can put it in.

Thanks!

--Dan