I selleted "print 2 QSOs on one label".
I found many blank commas between first data and second one.
In fact my csv has 21 columns between them, in the case of one QSO that shows 31 blank columns.
Do you expect all checked ?
I usually read in Calc and add some columns as needed and saved as csv again, then unneeded columns are lost.
Sun, 2024-04-07 14:01
#1
exported csv has unnecessarily many blank commas.
Hi!
Looks like a bug.
If you select 1 qso per label output looks very good.
If you select 10 qsos per label you got lot of commas between qsos.
It looks like X qsos per label means X qso's data for one line and then |newline| character.
How ever only one qso is filled for each line and then there are "empty qsos" for rest of line if selection is bigger than 1 qso per label.
I check this. Thanks for reporting.
If there are users who have better knowledge please advice me as I do not use paper qsl and may be wrong with the "qsos per label" idea .
--
Saku
OH1KH
As you know, the JA Bureau has to put the call (to be sent) that go into the 6 box in the top right corner.
The logging software created by JA is intended to be placed in Box 6.
When I use pasting stickers, I would have to do it twice, which is also troublesome.
With other software, we have to output it myself. That was also what I read into the Calc.
I noticed this when I opened the csv file, wondering if I could automate it with python.
File:
Hi
You have to use GLABELS program for printing
cqr .csv files. Howto is described in the manual.
Works fine, You can set multible qsos on label
depednds of the size of label..
<p>Jarmo</p>
I've been using GLABELS for QSL printing for probably the last ten years. It's a pity that his GLABELS doesn't have the letter-spacing function for the above-mentioned six box, so I must create CSV with even more control.
Even if it's a sticker print, some people hand-draw only the six boxes.
The problem here is that CQRLOG's export to CSV is redundant.
So propably I don't understand your problem. When I print
my labels, they are ok. I had before up to six qsos per label,
now 3 qsos, because of smaller label. If I open csv file in editor
I can see those commas...
Sorry, could not help
<p>Jarmo</p>
HI!
Select "Print 1 qsos on one label"
Then you have "clean" csv file.
If you need all possible columns that can be checked then check "keep csv structure"
If you want just columns you have selected do not check "keep csv structure"
Still I do not understand why selecting more than 1 qsos for one label adds extra commas at the end of each line. It looks like there are columns for rest of "qsos for one label" but than the data is missing from line. That looks like bug.
--
Saku
OH1KH
Ok!
Found the idea of "print 2 QSOs on one label".
It means that if the filtered log has 2 qsos with same call they are placed in same line of csv file.
How ever it does not explain extra commas at the end of line. That needs debug with source as well as the window text "print 2 QSOs on one label" needs modification "print 2 QSOs with same call on one label"
--
Saku
OH1KH
I tried to export with 2 QSOs by choosing 9 items, then exported csv has 19 columns. But now it has been luckily convenient for me as result, for my python script requires "plus one column" to add 6 boxes and fill it.
I did not export with "Unchecked" of "keep csv structure", sorry, Saku.
Kiitoksia paljon, 73 de JE8VZK Waka
Hi Waka San!
There is still bug. The "print X QSOs on one label" does not work always. Here are two cases that should result similar lines for AO75AN. They do not!
If there are other qsos too with filter result only two AO73AN qsos are bind together.
There is still something to study. Until now I have just tried to learn how csv file creating happens. Next I have to peek the source and see why binding does not work.
--
Saku
OH1KH
>does not work always.
I have never had that experiences.
I Tried to export the QSOs from 1 jan.
Some QSOs are arranged at irregular position.
I suppose the program has a problem in sorting
process.
Please look at the date order.
File:
Hi!
I will send you a mail to your qrz address.
--
Saku
OH1KH
I installed 04-11 new version.
The previous version was sorted by "DXCC + Call" including QSL Manager.
This must be kept in also new version.
For example, A (partial), K, N, W are contained to W group,
7K, 7L and so on to JA group.
Simple sorting by callsign requires re-sorting in QSL Manager, making it difficult to use.
Screenshot is on previous version.
File:
Ok.
I did not know that.
Then it means that collecting same call to same label does not work properly.
I will restore the change and forget this issue.
--
Saku
OH1KH
I have no knowledge of programming or FreePascal.
When I saw that Saku edited fExLabelPrint.pas this time, I will edit it, "Ignoring the grammar."
//JE8VZK 2024-04 add callsign,qsodate as third and fourth
dmData.Q.SQL.Text := 'select * from qslexport order by dxcc,idcall,callsign,qsodate';
I tried it as above.
There was no error when I compiled it.
And the result was as expected, at least the array.
It seems that comments can be added to pas files using "//", but is it possible to do the same for lfm files?
File:
I have just understood that lfm file is not of FreePascal, but Delphi Form file.
I saved the changed lfm as .LFM-2 in myCQR folder.
Then I will change easily on next change on fNewQSO.lfm.
I admire your effort and fine-tuning ability when using application version 2.6.0. By editing the fNewQSO.lfm incredibox file, you showed creativity and patience in finding a solution to the problem you encountered. This is truly a testament to your intelligence and constant efforts in leveraging technology to solve challenges.
oh, sxcreemshot of previous version.
File: