Hi Erwin,
let me explain how I setup a contest (but maybe there is a better way).
I have a directory called tlf, which is divided into sub-directories
which all have a contest name. Below the contest name is the date (in
case a contest happens more than once a year) or the year. Once I
created the directory structure for the contest which is coming up, I
copy all the data from the previous contest. This includes logcfg.dat,
the rules file, but also any sections file or exchange file. Then I do a
check of all the files, start winkeydaemon, open a terminal with a big
font, go into that directory and start tlf.
So for me, number one would be most convenient. I check my files anyway,
also after the contest I go into the cabrillo file and do a review.
But I am not very critical, whatever is easiest for you is okay with me.
I will adapt ;-)
73 de Joop PG4I
Ervin Hegedüs schreef op 2019-11-21 22:49:
Hi all,
On Sun, Nov 17, 2019 at 10:32:16AM +0100, Joop Stakenborg wrote:
It would be nice to have a cabrillo template. If present, all the
questions
when exporting to cabrillo can be skipped.
a few days ago I reviewed the possibilities, now I'ld like to discuss
them here.
1. the most simple way when we add new keywords to the config
files, eg. CABRILLO_CONTEST, CABRILLO_CALLSIGN, ...
therefore you can use these keywords both in logcfg.dat and
contest rule files
PRO: easy to make it
CON: you have to add the keywords everytime when you
prepare a new contest
2. read the new keywords from separated file; there are two
sub-solution in this case
a. this file could contains only the CABRILLO related options
PRO: clear and elegant solution
CON: hard to implement, makes the code logic more
complicated and horrible
b: this fie could any keyword, we just "call it" as "CABRILLO"
file
PRO: *could* be clear, easy to implement
CON: can lead to chaos (user can mix the options and can't
see the reason of the different bevaiour)
Let's start to discuss :).
I prefer 2/b.
73, Ervin
HA2OS
