[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xlog-discussion] Possible feature?
From: |
Pierfrancesco Caci |
Subject: |
Re: [Xlog-discussion] Possible feature? |
Date: |
Mon, 19 Aug 2013 22:25:41 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux) |
>>>>> "Andy" == Andy Stewart <address@hidden> writes:
Andy> I wonder how often people actually merge logs.
a bunch of times every few months.
I keep one file per month, and separate files for each contest. Then
every now and then I merge everything back into a single file
encompassing 6 months (if I've actually been on air...) or one whole
year. Since merging can only work on 2 files at a time, I have to
reiterate a bit.
The reason for the separate files is that any mistake is easier to
correct if I'm messing with smaller files.
Andy> While we're on the subject of possible future features, here's what I
Andy> was thinking prior to your email:
Andy> a) When exporting QSOs to a file, automatically X the "QSL out" column
Andy> for the exported QSOs. Naturally, this would be on/off at the behest
Andy> of the user, probably on a per-export basis. My usage model is to
Andy> Export to ADIF prior to uploading to eQSL and LoTW, thus I want to X
Andy> the "QSL out" column for those QSOs.
I only mark qsl sent for actual paper qsls. Can you make your "mark qsl
out" as an additional dialog during export? That way if I ever get
around doing the label thing, instead of actually writing the qsl cards
by hand, I could mark those that are being exported as done.
Today, I close Xlog, edit the
Andy> file with emacs, put Xs in the proper column, close the file, and
Andy> restart XLog. Painful IMHO! More generically, maybe there should be a
Andy> way to mark a group of QSOs like this...maybe the user just sent a
Andy> pile of QSL cards or something.
checkboxes? could that be practical? present a slightly different view
of the log with a check mark, let user select the qsos, then ask what to
do with them, with choices being export, mark qsl sent, etc..
Andy> b) I'm looking at what it would take to automatically interface with
Andy> eQSL. One could upload to eQSL as each QSL is logged, or a group of
Andy> QSOs. The upload looks easy. Dealing with the myriad error cases
Andy> looks frightful. Maybe as I look deeper, it won't be so bad.
you may want to have a look at what fldigi does for the error
handling.
--
Pierfrancesco Caci, ik5pvx