On Wed, March 28, 2012 12:24, Dan Smith wrote:
Also, I'm not happy with the loop that converts the data to the name in get_memory. It's possible the loop will never terminate, since there is no guarantee there will be an 0xFF byte present. Instead I will make it loop over rf.valid_name_length bytes (and terminate early if 0xFF is found).
No, because mem.name is bounded in length, so it will end before it runs over.
...is the right answer. I see that now.
My next task is to make a whole bunch of memories on the radio that differ by only one option setting, then dump the data and see what bits have changed. Then I can define them and unpack them properly.
Yep, welcome to the party :) Be sure to enable the developer features which provide the graphical diffing of two memories, which is handy. Also, note that several of us hang out on #chirp on FreeNode during the US day.
Thanks. I turned on the developer functions in the Help menu, but when I select View|Developer|Show raw memory, nothing happens. No message in the console either. Should I see a new window, or new columns in the main window? Diff raw memories does nothing either.
I am using CHIRP 0.1.12 with GTK 2.12.12 and PyGTK 2.12.1 under Linux 2.6.27and KDE 3.5.
I am in South Korea. During the US day I am either asleep, or at work. I'll try to do what I can alone, and use this email list when I am stuck.
73,
A