[chirp_users] programming assistance

[Jim Unroe]

On Wed, Jan 10, 2024 at 8:43 AM Roger Jane via chirp_users
<chirp_users at intrepid.danplanet.com> wrote:
>
> > >so I can't verify this. Perhaps it would be possible to have CHIRP always resync with the beginning of the CSV file's next line when a linefeed is encountered? Jim KC9HI
> > Absolutely common sense. Would be surprised were it not already the case...
>
> Very much looks to me as if it is already the case.  The csv data is read using a standard python csv library and parsed line by line.  Any data that is 'missing' is simply skipped over when it's being read into memory.  This is not 'exactly' the same action as a blank field (missing skips the data, blank sets it to 'None') but I would expect the overall effect to be the same.  If anyone wants to investigate, the place to look would seem to be the _parse_csv_data_line() function in generic_csv.py.
>
> Rog (hoping he's helping rather than complicating!)

It might be the case, but it doesn't fully mitigate the issue. I took
one of my saved img files and saved it as a csv file. I then loaded
the csv to make sure that it loaded OK. It did. I then use a text
editor to remove 2 commas from the end of the row for memory 5. The
file is loaded but memory 5 is missing. So at least the memory row
that is missing the trailing commas did not prevent the rest of the
csv file from loading. So apparently the library used is somewhat
better in CHIRP-next than it is in classic CHIRP, because loading the
file in classic CHIRP fails.

Jim KC9HI