Importing DX Labels [fixed in v1.666]

edited April 10 in Problems Now Fixed

I'm generating a csv of the original lables (ie what Kiwi ships with) and adding in the HFCC A24 database.

One curiosity (annoyance) that I've found it is that a row in the csv such as

15125;"AM";"CRI (Eng)";"BEI";;"T3";-4000;4000;;;'0000;'0100

loses the time schedule information once imported.

In the DX Tab it has no time schedule and on re-exporting to csv it shows it has become

15125;"AM";"CRI (Eng)";"BEI";;"T3";-4000;4000;;;;;

I can work around this either by editing the row in the DX tab, where it allows 0000 for the start and uses it, or by putting 2400 in the csv that I import, so the csv row becomes

15125;"AM";"CRI (Eng)";"BEI";;"T3";-4000;4000;;;'2400;'0100

But it's inelegant.

Similarly a csv row such as

15160;"AM";"KBS (Eng)";"KIM";;"T3";-4000;4000;;;'2200;'2400

after importing shows

15160;"AM";"KBS (Eng)";"KIM";;"T3";-4000;4000;;;;;

I have to get around this by making the row in the csv

15160;"AM";"KBS (Eng)";"KIM";;"T3";-4000;4000;;;'2200;'0000

So in essence it appears the START time has to be between 0001 and 2400, and the end time between 0000 and 2359 for the information in the csv to be faithfully imported.

Comments

  • jksjks
    edited April 6

    Okay, now fixed in the next release.

    This was just a bug in the code that imports the CSV files. Internally the condition that specifies no time interval is start,stop = 0,2400 or 0,0. My code to filter out these values from the CSV file import was faulty. The '0000;'0100 and '2200;'2400 cases now work fine.

  • Thank you

Sign In or Register to comment.