UKEIDX-CW this weekend

2020-02-22 Thread Joop Stakenborg
I have set up a rules file (ukeidxcw) and a multiplier list (ukeidxmults)
for this contest. Seems to work okay here. This is for stations outside
UK/EI. You can find them attached.

73 de Joop PG4I


ukeidxmults
Description: Binary data


ukeidxcw
Description: Binary data


Re: HA-DX Contest

2020-01-16 Thread joop . stakenborg
Hi Slav,Hope you will get there!There are not many cwops in Ireland...73! JoopOp 16 jan. 2020 20:45 schreef SP3RXO :Hi Joop,
Thank you,
Indeed, It was my 2nd or 3 attempt. Just for fun. Am I planning? First
I'm working hard to improve my cw skills. Contests are easy ;)  but rag
chewing at 25wpm is still too fast for me :/

73!
Slav, SP3RXO & EI2IDB
FISTS #19019
SOC #1251
SP CW Club #UNKNOWN

W dniu 16.01.2020 o 19:17, Joop Stakenborg pisze:
> On Thu, 16 Jan 2020 15:05:08 +
> SP3RXO  wrote:
> 
>> 73!
>> Slav, SP3RXO & EI2IDB
>> FISTS #19019
>> SOC #1251
>> SP CW Club #UNKNOWN
> 
> Hi Slav,
> 
> I saw you participated in the CWT mini contest yesterday. Do you plan on becoming a CWOPS member? Tlf works great in the CWT!
> 
> 73 de Joop PG4I
> CwOPS #2225
> 



can we benefit from N1MM's UDC files?

2019-12-19 Thread Joop Stakenborg
N1MM has a large collection of so called UDC (User Defined Contest) 
files, see:


https://n1mmwp.hamdocs.com/mmfiles/categories/userdefinedcontests

They are packed into a zip file which contains a udc file with a 
description of the contest, but there are also member lists and other 
stuff. The udc files contains contest and scoring information. I have 
looked into it quickly and at first it seems complicated but I am sure 
it is well documented and there also seems to be a dedicated editor for 
udc files (in exe format of course).


We could benefit from this large library, although I don't know what the 
licensing issues might be when including them with tlf.



Just a thought,

73 de Joop PG4I




Re: pywinkeyerdaemon

2019-11-29 Thread Joop Stakenborg

Hi Drew,


is pywinkerdaemon intended to work with USB ports? I get:

$ ./pywinkeyerdaemon.py -d /dev/ttyUSB1 -p 6788
Traceback (most recent call last):
  File "./pywinkeyerdaemon.py", line 310, in 
    winkeyer = Winkeyer(args.device)
  File "./pywinkeyerdaemon.py", line 43, in __init__
    self.host_open()
  File "./pywinkeyerdaemon.py", line 57, in host_open
    assert self.port.read(1).decode() == test_char
AssertionError


Joop PG4I

Op 26-11-19 om 00:44 schreef Drew Arnett:

Finally knocked off some todos including porting to python3.  (still
runs on 2 as well)

Also, finally added in message +/- controls (tested with TLF) and
support for cwdaemon prosigns.  (I hadn't been using these sorts of
things, so hadn't missed them personally, but they've
been on the TODO list too long.)

+++TEST--- doesn't work unless there's a setspeed first.  (I didn't
find that function in the winkeyer interface.)  In testing, I found
that tlf sends a setspeed command at startup, so no problems.

https://github.com/drewarnett/pywinkeyerdaemon

Best regards,

Drew
n7da





Re: tlf and the nano editor

2019-11-25 Thread Joop Stakenborg

Hi Tom,


It works okay with 'nano' now, thanks!

The weekend was, fun. Made mores than 800 Q's in the CQWWCW with tlf and 
winkeydaemon using the nanokeyer.


73 de Joop PG4I


Op 23-11-19 om 19:33 schreef Thomas Beierlein:

Hi,

please see the improved version on the same link as yesterday.

 From the commit message:


Improve editor handling

- Uses it also for :CFG and :SET commands
- Fall back to editor defined in environment if not defined in
  logcfg.dat
- Show warning if editor program not found

@nate: I tested it with gedit and gvim -> works. What is emacs doing?


73, de Tom DL1JBE


Am Fri, 22 Nov 2019 20:19:53 +0100
schrieb Thomas Beierlein :


Hi all,

as the fixed choice of editors is quite a nuisance I prepared a
changed version for tests. Please find it at
https://github.com/dl1jbe/tlf/tree/new_editor

Download the code and build TLF as told in the INSTALL file. Do not
forget the 'autoreconf -i' step.

The new version accepts any string as editor command and will just
call that program with the logfile name as parameter.

That means

EDITOR=my-shiny-editor

in logcfg.dat will call

'my-shiny-editor '

So a simple EDITOR=nano should do afterwards.

Please test and give feedback.

73, de Tom DL1JBE

Am Fri, 22 Nov 2019 11:08:52 -0600
schrieb jim smith :


On Fri, 22 Nov 2019 15:06:14 +0100
Joop Stakenborg  wrote:
   

I have gotten used to the GNU nano editor, but it does not seem to
work with tlf. When I type :edit in the callsign field, tlf exits
and returns straight away without opening nano. Both joe and vi
work okay here. It is hard to debug, have to spent some time on it
to see what actually happens. Maybe use gdb with a break added. I
will have a look next week.


73 de Joop PG4I
 


Hi Joop,

I don't know if this helps any, but I don't have any problems
running nano with tlf on ubuntu 18.04. I have *not* updgraded to
tlf 1.4 yet (was going to do that this weekend.










Re: tlf and the nano editor

2019-11-22 Thread Joop Stakenborg

Hi Tom,


it works okay for the :edit command, but you need to change the code for 
both the :set and :cfg commands (which allows editing of logcfg.dat), 
they both start the joe editor, even though I have EDITOR=nano in 
logcfg.dat.


The code is in changepars.c

Thanks,

Joop

Op 22-11-19 om 20:19 schreef Thomas Beierlein:

Hi all,

as the fixed choice of editors is quite a nuisance I prepared a
changed version for tests. Please find it at
https://github.com/dl1jbe/tlf/tree/new_editor

Download the code and build TLF as told in the INSTALL file. Do not
forget the 'autoreconf -i' step.

The new version accepts any string as editor command and will just call
that program with the logfile name as parameter.

That means

EDITOR=my-shiny-editor

in logcfg.dat will call

'my-shiny-editor '

So a simple EDITOR=nano should do afterwards.

Please test and give feedback.

73, de Tom DL1JBE

Am Fri, 22 Nov 2019 11:08:52 -0600
schrieb jim smith :


On Fri, 22 Nov 2019 15:06:14 +0100
Joop Stakenborg  wrote:


I have gotten used to the GNU nano editor, but it does not seem to
work with tlf. When I type :edit in the callsign field, tlf exits
and returns straight away without opening nano. Both joe and vi
work okay here. It is hard to debug, have to spent some time on it
to see what actually happens. Maybe use gdb with a break added. I
will have a look next week.


73 de Joop PG4I
   


Hi Joop,

I don't know if this helps any, but I don't have any problems running
nano with tlf on ubuntu 18.04. I have *not* updgraded to tlf 1.4 yet
(was going to do that this weekend.







Re: tlf and the nano editor

2019-11-22 Thread Joop Stakenborg
Forgot to edit tlf.1.in. Sorry!


> Op 22 nov. 2019, om 16:10 heeft Joop Stakenborg  
> het volgende geschreven:
> 
> Ah well... might as well add it right away, seems to work okay here. Diff 
> attached!
> 
> 
> 
> Joop
> 
> Op 22-11-19 om 15:35 schreef joop.stakenb...@xs4all.nl 
> <mailto:joop.stakenb...@xs4all.nl>:
>> Thanks Nate! Looks really simple... Will try it out next week.
>> 
>> Joop
>> 
>> Op 22 nov. 2019 15:13 schreef Nate Bargmann  
>> <mailto:n...@n0nb.us>:
>> * On 2019 22 Nov 08:07 -0600, Joop Stakenborg wrote: 
>> > I have gotten used to the GNU nano editor, but it does not seem to work 
>> > with 
>> > tlf. When I type :edit in the callsign field, tlf exits and returns 
>> > straight 
>> > away without opening nano. Both joe and vi work okay here. It is hard to 
>> > debug, have to spent some time on it to see what actually happens. Maybe 
>> > use 
>> > gdb with a break added. I will have a look next week. 
>> 
>> It should be fairly simple as I added mcedit to the list of available 
>> editors.  A quick 'git grep mcedit' shows where mcedit was added: 
>> 
>> $ git grep mcedit 
>> ChangeLog:1117:  * share/logcfg.dat, src/editlog.c, src/parse_logcfg.c: 
>> Prefer 'mcedit' for 
>> ChangeLog:1119:  Enable 'mcedit' as a log file editor. 
>> share/logcfg.dat:33:#EDITOR=mcedit 
>> src/changepars.c:359:   strcpy(cmdstring, "mcedit "); 
>> src/editlog.c:63:   strcat(comstr, "mcedit  "); 
>> src/parse_logcfg.c:904: if ((strncmp(buff, "mcedit", 6) == 0) 
>> tlf.1.in:282:Edit the log with your favourite editor (the editor 
>> (vi[m]|joe|e3|mcedit) 
>> tlf.1.in:975:You can set your favourite editor (joe | vi[m] | e3 | mcedit) 
>> in the 
>> tlf.1.in:1047:\fBEDITOR\fR=\fIjoe\fR | \fIvi\fR[\fIm\fR] | \fIe3\fR | 
>> \fImcedit\fR 
>> 
>> This should help you get started, Joop. 
>> 
>> 73, Nate 
>> 
>> -- 
>> 
>> "The optimist proclaims that we live in the best of all 
>> possible worlds.  The pessimist fears this is true." 
>> 
>> Web: https://www.n0nb.us <https://www.n0nb.us/> 
>> Projects: https://github.com/N0NB <https://github.com/N0NB> 
>> GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 
>> 
>> 
>> 
> 



Re: tlf and the nano editor

2019-11-22 Thread Joop Stakenborg
Ah well... might as well add it right away, seems to work okay here. 
Diff attached!



Joop

Op 22-11-19 om 15:35 schreef joop.stakenb...@xs4all.nl:

Thanks Nate! Looks really simple... Will try it out next week.

Joop

Op 22 nov. 2019 15:13 schreef Nate Bargmann :

* On 2019 22 Nov 08:07 -0600, Joop Stakenborg wrote:
> I have gotten used to the GNU nano editor, but it does not seem
to work with
> tlf. When I type :edit in the callsign field, tlf exits and
returns straight
> away without opening nano. Both joe and vi work okay here. It is
hard to
> debug, have to spent some time on it to see what actually
happens. Maybe use
> gdb with a break added. I will have a look next week.

It should be fairly simple as I added mcedit to the list of available
editors.  A quick 'git grep mcedit' shows where mcedit was added:

$ git grep mcedit
ChangeLog:1117:  * share/logcfg.dat, src/editlog.c,
src/parse_logcfg.c: Prefer 'mcedit' for
ChangeLog:1119:  Enable 'mcedit' as a log file editor.
share/logcfg.dat:33:#EDITOR=mcedit
src/changepars.c:359:   strcpy(cmdstring, "mcedit ");
src/editlog.c:63:   strcat(comstr, "mcedit  ");
src/parse_logcfg.c:904: if ((strncmp(buff, "mcedit", 6) == 0)
tlf.1.in:282:Edit the log with your favourite editor (the editor
(vi[m]|joe|e3|mcedit)
tlf.1.in:975:You can set your favourite editor (joe | vi[m] | e3 |
mcedit) in the
tlf.1.in:1047:\fBEDITOR\fR=\fIjoe\fR | \fIvi\fR[\fIm\fR] |
\fIe3\fR | \fImcedit\fR

This should help you get started, Joop.

73, Nate

-- 


"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819


diff --git a/src/changepars.c b/src/changepars.c
index 02970c1..2d5bbb1 100644
--- a/src/changepars.c
+++ b/src/changepars.c
@@ -358,6 +358,8 @@ int changepars(void) {
 		strcpy(cmdstring, "vi ");
 	} else if (editor == EDITOR_MC) {
 		strcpy(cmdstring, "mcedit ");
+	} else if (editor == EDITOR_NANO) {
+		strcpy(cmdstring, "nano ");
 	} else {
 		strcpy(cmdstring, "e3 ");
 	}
diff --git a/src/editlog.c b/src/editlog.c
index e11c140..bf82bdb 100644
--- a/src/editlog.c
+++ b/src/editlog.c
@@ -53,6 +53,8 @@ int logedit(void) {
 	strcat(comstr, "vi  ");
 else if (editor == EDITOR_MC)
 	strcat(comstr, "mcedit  ");
+else if (editor == EDITOR_NANO)
+	strcat(comstr, "nano  ");
 else
 	strcat(comstr, "e3  ");
 
diff --git a/src/parse_logcfg.c b/src/parse_logcfg.c
index 43b53a4..0de1085 100644
--- a/src/parse_logcfg.c
+++ b/src/parse_logcfg.c
@@ -934,6 +934,11 @@ int parse_logcfg(char *inputbuffer) {
 	if (j != NULL) {
 		editor = EDITOR_VI;
 		break;
+	}
+	j = strstr(fields[1], "nano");
+	if (j != NULL) {
+		editor = EDITOR_NANO;
+		break;
 	} else {
 		editor = EDITOR_E3;
 		break;
diff --git a/src/tlf.h b/src/tlf.h
index ae11b76..61b5a61 100644
--- a/src/tlf.h
+++ b/src/tlf.h
@@ -119,6 +119,7 @@ enum {
 #define EDITOR_VI 1
 #define EDITOR_E3 2
 #define EDITOR_MC 3
+#define EDITOR_NANO 4
 
 #define UNIQUECALL_ALL  1
 #define UNIQUECALL_BAND 2


Re: tlf and the nano editor

2019-11-22 Thread joop . stakenborg
Thanks Nate! Looks really simple... Will try it out next week.JoopOp 22 nov. 2019 15:13 schreef Nate Bargmann :* On 2019 22 Nov 08:07 -0600, Joop Stakenborg wrote:
> I have gotten used to the GNU nano editor, but it does not seem to work with
> tlf. When I type :edit in the callsign field, tlf exits and returns straight
> away without opening nano. Both joe and vi work okay here. It is hard to
> debug, have to spent some time on it to see what actually happens. Maybe use
> gdb with a break added. I will have a look next week.

It should be fairly simple as I added mcedit to the list of available
editors.  A quick 'git grep mcedit' shows where mcedit was added:

$ git grep mcedit
ChangeLog:1117:  * share/logcfg.dat, src/editlog.c, src/parse_logcfg.c: Prefer 'mcedit' for
ChangeLog:1119:  Enable 'mcedit' as a log file editor.
share/logcfg.dat:33:#EDITOR=mcedit
src/changepars.c:359:   strcpy(cmdstring, "mcedit ");
src/editlog.c:63:   strcat(comstr, "mcedit  ");
src/parse_logcfg.c:904: if ((strncmp(buff, "mcedit", 6) == 0)
tlf.1.in:282:Edit the log with your favourite editor (the editor (vi[m]|joe|e3|mcedit)
tlf.1.in:975:You can set your favourite editor (joe | vi[m] | e3 | mcedit) in the
tlf.1.in:1047:\fBEDITOR\fR=\fIjoe\fR | \fIvi\fR[\fIm\fR] | \fIe3\fR | \fImcedit\fR

This should help you get started, Joop.

73, Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819




tlf and the nano editor

2019-11-22 Thread Joop Stakenborg
I have gotten used to the GNU nano editor, but it does not seem to work 
with tlf. When I type :edit in the callsign field, tlf exits and returns 
straight away without opening nano. Both joe and vi work okay here. It 
is hard to debug, have to spent some time on it to see what actually 
happens. Maybe use gdb with a break added. I will have a look next week.



73 de Joop PG4I




Re: feature request: cabrillo template

2019-11-21 Thread Joop Stakenborg

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




Re: getting ready for the CQWW CW

2019-11-21 Thread Joop Stakenborg

Yes it works, thank you Ervin!

PS. I feel stupid...

Joop PG4I

Op 21-11-19 om 22:39 schreef Ervin Hegedüs:

Hi Joop,

On Thu, Nov 21, 2019 at 10:30:35PM +0100, Joop Stakenborg wrote:

Hello girls and boys,


I can't seem to get the correct rules file for the CQWWCW this weekend. In
the CQWW both the CQ zone and the country count as a multiplier. I have:

MY_COUNTRY_POINTS=0
MY_CONTINENT_POINTS=1
DX_POINTS=3
MULT_LIST=zones.txt
DX_&_SECTIONS


Looks good okay?

just fyi, Tlf supports CQ-WW "out-of-box", this contest is
"hardcoded".

 From the man tlf:

It supports the CQWW, WPX, ARRL-DX, ARRL-FD, STEWPERRY, PACC and
EU SPRINT contests as well as a lot more basic contests, ...


so this is enough:

CONTEST=cqww
LOGFILE=cqww.log
CONTEST_MODE

...
F1=+++TEST ---% +++TEST---
F2=%
...


(note: of course, you can put more "+" to the begin of the TEST...  :))


The first QSO I make with DL1AA in zone 14: 1 point, 1 multiplier for
country (should be 2, one for country and one for section)

The second QSO with W2GD in zone 5: 3 points, 1 mutiplier for section
(should be 2, one for country and one for section)


Is my setup okay?

I think just try that one above.


73, Ervin
HA2OS


  




getting ready for the CQWW CW

2019-11-21 Thread Joop Stakenborg

Hello girls and boys,


I can't seem to get the correct rules file for the CQWWCW this weekend. 
In the CQWW both the CQ zone and the country count as a multiplier. I have:


MY_COUNTRY_POINTS=0
MY_CONTINENT_POINTS=1
DX_POINTS=3
MULT_LIST=zones.txt
DX_&_SECTIONS


Looks good okay?

The first QSO I make with DL1AA in zone 14: 1 point, 1 multiplier for 
country (should be 2, one for country and one for section)


The second QSO with W2GD in zone 5: 3 points, 1 mutiplier for section 
(should be 2, one for country and one for section)



Is my setup okay?

Regards,

Joop PG4I




Re: trouble scoring the LZ-DX contest

2019-11-18 Thread Joop Stakenborg



Op 17-11-19 om 18:19 schreef Thomas Beierlein:


But I fear there will be another combination of multipliers
poping up soon which we do not have in our repertoire.
So a better solution is needed - same goes for point scoring.

I did some investigation how other contest programs solve these problem.
One of the ideas there are to classify multipliers into some main
categories:

- Country/DXCC
- Zone CQ or ITU
- Prefix
- section or similar



Some contests, like cwops and FOC ones, have the callsign as a 
multiplier, crazy if you ask me!


But tlf can handle this with UNIQUE_CALL_MULTI=ALL, no problem!



With that we could allow more to count more than one category as multi
and would need additional rules how to combine the values (add if more
than one or score only one) and how to count on different
bands (BY-BAND or ONCE). Than your ITU_&_SECTION could be something
like:

COUNTRY_MULT = DXCC,BY_BAND
ZONE_MULT = ITU,BY_BAND ADD

I am not sure if that would catch all or at least most of the multi
scoring problems for existing contests.



I agree, we need a more flexible way of scoring. Right now it is quite a 
study to setup a contest with all the different keywords that tlf uses 
in the rules file. I am willing to do as much testing as you like.




Feedback on that is very much welcome.

73, de Tom DL1JBE


Thanks Tom!

73 Joop PG4I




Re: feature request: cabrillo template

2019-11-18 Thread Joop Stakenborg

Sounds good Ervin / Thomas!

I was thinking of a more simple solution, something like: if there is a 
template file in the current directory, just add the QSO data to it. The 
cabrillo file then should be edited later.


But.. the solution suggested by Ervin is even better, thumbs up!

73 de Joop PG4I


Op 18-11-19 om 19:01 schreef Thomas Beierlein:

Hi Ervin,

sounds good so far. If there are no other suggestions from Joop or
others just go ahead.

73, de Tom DL1JBE

  Am Sun, 17 Nov 2019 18:17:13 +0100
schrieb Ervin Hegedüs :


Hi all,

On Sun, Nov 17, 2019 at 06:00:41PM +0100, Thomas Beierlein wrote:

Hi Joop,

I assume you are talking about the contest and operator related
informations gathered when you want to write a new cabrillo file.

Can you please elaborate some more about what you have in mind here.
The head part of the cabrillo file is not independent of the
contest. So one template for all seems not to fit. But I see that
at least the operator related part could be common between contests.

Any comments or suggestions?

I don't want to answer for Joop, but I thought about this feature
earlier.

I imagined like this:

logcfg.dat:

CABRILLO_DATA=/home/airween/.tlf/HA2OS_general.cab
CABRILLO_CONTEST=CQ-WW-CW
...

/home/airween/.tlf/HA2OS_general.cab
CABROLLO_CALLSIGN: HA2OS
CABRILLO_LOCATION: DX
CABRILLO_CATEGORY-OPERATOR: SINGLE-OP
CABRILLO_CATEGORY-ASSISTED: NON-ASSISTED
CABRILLO_CATEGORY-BAND: ALL
CABRILLO_CATEGORY-POWER: LOW
CABRILLO_CATEGORY-MODE: CW
CABRILLO_CATEGORY-TRANSMITTER: ONE
CABRILLO_CATEGORY-OVERLAY:
CABRILLO_CONTEST=

I wrote deribelately the CABRILLO_CONTEST field at two places
(logcfg.dat and general data file): the second occurrance of
field overwrites the first, so therefore we can replace the
values at every contest, but can use a basic data.

When user types a ":w" in callsign field (start to export the log
to CABRILLO), then the fields which has values (by set them the
fields above) will filled in dialogues.

If you like this way, I can start to implement it soon.


73, Ervin
HA2OS









feature request: cabrillo template

2019-11-17 Thread Joop Stakenborg
It would be nice to have a cabrillo template. If present, all the 
questions when exporting to cabrillo can be skipped.



73 de Jo PG4I




trouble scoring the LZ-DX contest

2019-11-17 Thread Joop Stakenborg
First of all, thanks for the new release! I have started using tlf a few 
weeks ago, very happy!



I am having trouble scoring the lz-dx contest. Points are okay, but 
multipliers not. The multiplier is either the ITU zone or the LZ 
district. So I would like to have something like ITU_&_SECTIONS, which 
would work the same as DX_&_SECTIONS.



Here is part of my rules file, which does not work properly (lz_dx_mults 
attached):



#
#  CONTEST PARAMETERS
#
#
MULT_LIST=lz_dx_mults
COUNTRYLIST=LZ
SECTION_MULT
ITUMULT
#
#
#  POINTS LIST
#
#
COUNTRY_LIST_POINTS=10
MY_CONTINENT_POINTS=1
DX_POINTS=3



bu
bl
vn
vt
vd
vr
ga
do
ka
kd
lv
mn
pa
pk
pl
pd
rz
rs
ss
sl
sm
sf
so
sz
ta
ha
sn
ya

Re: CWOPS mini-CWT test rules and initial exchange

2019-11-05 Thread Joop Stakenborg



Op 05-11-19 om 15:34 schreef Thomas Beierlein:

Hi Joop,

looks good. Have fun.

73, de Tom DL1JBE

Btw, are there any objections (copyright or similar) to add teh
rulesand/or the member list to TLF's rule collection.



No, not at all Tom. Use them as you like!


Joop PG4I




CWOPS mini-CWT test rules and initial exchange

2019-11-05 Thread Joop Stakenborg

Hi folks,

The CWOPS mini-CWT test is a one-hour contest every wednesday from 
13-14z, 19-20z en 03-04z the next morning. You can participate as a 
CWOPS member or a non-member. You get 1 point per QSO, the multiplier is 
each call once. Exchange is either name+member number or name+country or 
state if you are not a member.


It is a fun contest with lots of activity, I use it a lot for testing 
antennas and setups. A log can be submitted at http://www.3830scores.com


Attached you can find the rules file and the cwops member list (up to 
2384) which can be used for INITIAL_EXCHANGE. Please change F3 and 
S_TU_MSG in the rules file to match your exch.


I will use tlf for the first time tomorrow in this contest! Wish me 
luck! ;-)



73 de Joop PG4I

CONTEST=cwops_mini_cwt
LOGFILE=cwops_mini_cwt.log
CONTEST_MODE
CABRILLO=UNIVERSAL
#
##
##
#  Messages F1= to F12=  #
#  Message CQ_TU_MSG=#
#  Message S_TU_MSG=   #
##
#  % = call  #
#  @ = hiscall   #
#  # = serial#
#  [ = RST   #
#  + = increase cw speed #
#  - = decrease cw speed #
##
##
#
F1=TEST % % CWT
F2=@ DE %
F3=@ JO 2225
F4=TU 73
F5= @
F6=%
F7=@ SRI QSO B4 GL
F8=AGN
F9= ?
F10= QRZ?
F11= PSE K
F12= TEST % % CWT
#
CQ_TU_MSG=TU %
S_TU_MSG=TU JO 2225
#
#   #
#  POINTS LIST  #
#   #
#
ONE_POINT
#
#   #
#  MULIPLIER#
#   #
#
UNIQUE_CALL_MULTI=ALL
RECALL_MULTS
#
#   #
#  EXCHANGE #
#   #
#
INITIAL_EXCHANGE=cwops.txt
# cwops member list up to number 2384
# last updated november 4, 2019
2E0OBO,Bob 2381
3W9T,Trung 1707
4K0CW,Axel 1678
4X4NJ,Riki 275
4X4PP,Pepe 1442
4X6GP,Vic 5
4X6KF,Falafel 659
4Z1UF,Ilya 636
4Z4DX,Dov 175
6Y2T,Yuri 21
6Y5WJ,Josh 186
7J1ABD,Dan 1176
7Q7M,Sue 2275
7X2TT,Abdel 2344
7X3DA,Hamid 1676
8P9AA,Yuri 21
8P9AL,Chuck 969
8P9NX,Peter 503
9A7R,Braco 1482
9N7DX,Dov 175
9V1VV,John 678
9V1YC,James 66
A61AD,Don 2
AA0FO,Marshall 1532
AA0RS,Dave 
AA1K,Jon 2055
AA1V,Don 53
AA2AD,Pete 2162
AA2ZW,Bob 937
AA3B,Bud 242
AA4CF,Charlie 1389
AA4FU,Alan 1121
AA4GA,Lee 973
AA4LS,Charles 2133
AA4MC,Hammer 2332
AA4NC,Will 2371
AA4NN,Joe 354
AA4NP,Jim 1954
AA4V,Steve 1867
AA5AD,Joe 2366
AA5BG,Richard 454
AA5W,Jim 1826
AA6MK,Mike 1909
AA6W,Don 2311
AA6XA,Jeff 2118
AA7FV,Darrel 1578
AA7ST,John 2263
AA7V,Steve 1250
AA8IA,Mike 966
AA8R,Randy 2214
AA8TA,Joe 1821
AA9A,Tom 1092
AA9K,Bob 1006
AB0DK,Dave 1932
AB0S,Tim 1857
AB1BX,Andy 2191
AB1CW,Howard 1117
AB1GJ,Ken 161
AB5EB,Mike 2115
AB5OR,Joe 1338
AB6UR,Danny 2315
AB6XG,Rick 1754
AB6Z,Tom 1664
AB7MP,Mark 1350
AB7RW,Phil 2249
AB9YC,Anthony 1249
AC0W,Bill 1564
AC1FE,Rich 783
AC2FA,Bob 1026
AC2K,Alan 35
AC2KJ,Dima 1376
AC3BU,Daryl 2355
AC4BT,Jerry 1148
AC4CA,John 650
AC5K,Wes 54
AC6AC,Buz 1911
AC6YY,Ned 1244
AC7JW,Jason 627
AC7T,Doug 822
AC8W,Stan 695
AC9EZ,Jim 2342
AD0AB,Jim or Jaime 2114
AD0DX,Ron 1019
AD0IU,Rob 864
AD0WE,Kurt 2167
AD1C,Jim 131
AD4EB,Jim 867
AD4ES,Chuck 2044
AD4J,Jim 1144
AD4TJ,David 1960
AD5A,Mike 1415
AD6E,Al 217
AD6JV,Bill 1719
AD8CW,Doug 412
AD8J,John 1395
AE0P,Brian 1051
AE1T,Peter 1404
AE2U,Mike 869
AE4QQ,Dave 1625
AE4Y,Kent 2002
AE6Y,Andy 38
AE7US,Rocky 1781
AF1Z,Mark 258
AF3K,John 2186
AF4NC,Tom 1521
AF5DM,Dave 1205
AF5Q,Ron 1805
AF8A,Gary 2092
AF9W,Bob 1173
AG3R,Pete 467
AG4EA,Bill 2373
AG5M,Rich 1747
AG6V,Donna 911
AG6WJ,Diego 2165
AG9A,Mark 641
AH0U,Bruce 1825
AH6KO,Stan 1794
AH6RE,Curt 830
AI2Q,Alex 210
AI6O,Ed 1337
AI6V,Wyatt 2242
AJ1DM,John 1973
AJ4HP,O 1467
AJ6DU,Ted 2269
AJ8B,Bill 1567
AK4AO,Doug 2145
AK4NY,Tom 1544
AK4SQ,Dan 1296
AL1G,Corliss 2161
AO1AAW,Juanjo 714
BA4TB,Dale 259
BH4EPL,Bruce 2297
C6AQQ,Brian 302
C6AUM,Mike 1182
CE2LR,Matt 2281
CM8NMN,Noe 2082
CN8YR,Med 1656
CO2IR,Frank 1147
CO6RD,Rey 1898
CO8ZZ,Raúl 1682
CT7AGZ,Ken 2126
CU3AA,Joao 1804
CX6VM,Jorge 525
CX7CW,Phil 570
CX7TT,Tom 518
DD5CF,Colin 1832
DD5XX,Saki 2354
DF4XX,Kurt 1753
DJ0MCH,Relly 409
DJ0QN,Mitch 747
DJ1OJ,Heijo 425
DJ1YFK,Fabian 1566
DJ7AO,Steve 2254
DK1WI,Ed 1602
DK4LX,Holger 802
DK5AX,Markus 1812
DK5KK,Kolja 1965
DK9PY,Armin 2062
DL1IAO,Stef 1884
DL1QQ,Sandy 1581
DL1REM,Frank 2382
DL2CC,Frank 511
DL3AZ,Andy 982
DL3DXX,Mar 1164
DL4FDM,Fri 1084
DL5AXX,Ulf 1517
DL5DBY,Tom 1751
DL5JQ,Hardy 2376
DL5XL,Felix 2268
DL6KVA,Axel 1678
DL8PG,Gerd 833
DL9ABM,Stefan 1922
DM1TT,Hannu 333
DM4CW,Martin 1870
DO4DXA,Marc 1851
DU3LA,Larry 644
E21EIC,Champ 264
E71A,Emil 484
EA1WX,Juanjo 714
EA2AJB,Sparky 1048
EA3/K1MM,Bill 43

Re: OK/OM DX Contest

2019-11-04 Thread Joop Stakenborg

Thanks!

For the first time I see the initial exchange working, it is great!

Joop PG4I

Op 04-11-19 om 18:16 schreef SP3RXO:

The OK / OM competition will take place over the weekend, Saturday
12:00UTC - Sunday 12:00UTC. I made a rules file for non OK/OM stations
(nothing complicated this time, hi), the most important part is:

#
MULT_LIST=ok_ommults
COUNTRYLIST=OK,OM
USE_COUNTRYLIST_ONLY
COUNTRY_LIST_POINTS=1
SECTION_MULT
RECALL_MULTS
INITIAL_EXCHANGE=ok_om.txt
SERIAL_EXCHANGE
#

If you are DX station, change COUNTRY_LIST_POINTS to 3 points.
The rest of the rules file depends on your preferences.

I attach 2 files:
- ok_ommults with ok/om multipliers
- ok_om.txt for initial exchange

Any comments are very welcome.

Feel free to use if you like.
GL!






Re: scoring the HSC contest with tlf

2019-11-04 Thread Joop Stakenborg

Hello Slav,


have you checked my rules file for the URDX?

The very first QSO with UR correctly counts 2 multipliers and 10 points. 
I have just checked with a new log.



Regards,

Joop PG4I


Op 04-11-19 om 10:48 schreef SP3RXO:

Hi all,
Below is part of my rules file for URDX Contest.
The only problem is that multiplier for very first qso with UR station
should be 2: 1 for UR district and 1 for dxcc. Have no idea how to do it
with tlf rules?

#
COUNTRYLIST=UR
COUNTRY_LIST_POINTS=10
MY_COUNTRY_POINTS=1
MY_CONTINENT_POINTS=2
DX_POINTS=3
MIXED
MULT_LIST=urdxc_mult
DX_&_SECTIONS
#SERIAL_EXCHANGE
SERIAL_OR_SECTION
RECALL_MULTS
INITIAL_EXCHANGE=UKRAINDX.txt
#

73!
Slav, SP3RXO & EI2IDB
FISTS #19019

W dniu 04.11.2019 o 08:37, Joop Stakenborg pisze:

Hoi Koos!


Op 03-11-19 om 20:46 schreef Koos van den Hout PE4KH:

On 11/3/19 5:41 PM, Joop Stakenborg wrote:


I have been using tlf 2 times today: during the ukrainian DX contest and
the HSC CW contest. I have managed to write a rules file for the
ukrainian, but not for the HSC.

Please share the rules file you made for the ukranian DX contest with
the list so it can be included in a future version of tlf.

Compared to other contest software TLF could use support for some more
contests. So if you create a rules file that works please share it so
others can test/improve it and it can be added to the distributed
archive (so please share your files with the same license as tlf itself).


Here it is. See the attachments, I have added a .txt extension so your
email programs wil recognize it as a text file. My logcfg.dat contains a
first line with RULES=ukrainian_dx, pointing to the file ukrainian_dx in
the rules directory.

I am unsure if the multiplier list needs the '-end-' line, must have
look at the source code. It is not mentioned in the manual page.


   Just a thought from a satisfied user!

Koos PE4KH


Joop PG4I





Re: scoring the HSC contest with tlf

2019-11-04 Thread Joop Stakenborg

Hoi Koos!


Op 03-11-19 om 20:46 schreef Koos van den Hout PE4KH:

On 11/3/19 5:41 PM, Joop Stakenborg wrote:


I have been using tlf 2 times today: during the ukrainian DX contest and
the HSC CW contest. I have managed to write a rules file for the
ukrainian, but not for the HSC.

Please share the rules file you made for the ukranian DX contest with
the list so it can be included in a future version of tlf.

Compared to other contest software TLF could use support for some more
contests. So if you create a rules file that works please share it so
others can test/improve it and it can be added to the distributed
archive (so please share your files with the same license as tlf itself).



Here it is. See the attachments, I have added a .txt extension so your 
email programs wil recognize it as a text file. My logcfg.dat contains a 
first line with RULES=ukrainian_dx, pointing to the file ukrainian_dx in 
the rules directory.


I am unsure if the multiplier list needs the '-end-' line, must have 
look at the source code. It is not mentioned in the manual page.


  
Just a thought from a satisfied user!


Koos PE4KH



Joop PG4I


#  Ukrainian DX contest#
#  for stations outside of Ukraine #

#
CONTEST=ukrainian_dx
LOGFILE=ukrainian_dx.log
CONTEST_MODE
CABRILLO=UNIVERSAL
SHORT_SERIAL
#
#
#   #
#  CONTEST PARAMETERS   #
#   #
#
#
MULT_LIST=ukrainian_dx_mults
COUNTRYLIST=UR
DX_&_SECTIONS
SECTION_MULT
SERIAL_EXCHANGE
#
#
#   #
#  POINTS LIST  #
#   #
#
#
COUNTRY_LIST_POINTS=10
MY_COUNTRY_POINTS=1
MY_CONTINENT_POINTS=2
DX_POINTS=3
##
F1=CQ DE % % TEST
F2=@ DE %
F3=@ 5NN #
F4=TU 73
F5=@
F6=%
F7=@ SRI QSO B4 GL
F8=AGN
F9=?
F10=QRZ?
F11=PSE K
F12=TEST % %
#
CQ_TU_MSG=TU %
S_TU_MSG=TU 5NN #
### END #
SU
TE
CH
ZA
DN
OD
HE
PO
DO
KR
SL
RI
HA
LU
VI
VO
ZP
CR
IF
HM
KO
KV
KI
LV
ZH
CN
NI
-end-


scoring the HSC contest with tlf

2019-11-03 Thread Joop Stakenborg

Good afternoon,


I have been using tlf 2 times today: during the ukrainian DX contest and 
the HSC CW contest. I have managed to write a rules file for the 
ukrainian, but not for the HSC.


Does anyone know how to do this? Multiplier is easy enough with 
COUNTRY_MULT but how do you score points? It is 5 points for member, who 
send their member number and 1 point for non-members, who send 'NM'.


Also, is there a way for tlf to automatically fill in the member number 
in the exchange field, like yfktest does?



Regards,

Joop PG4I, HSC #1100




Re: [Tlf-devel] fldigi tlf

2007-11-23 Thread Joop Stakenborg

Op vrijdag 23-11-2007 om 04:27 uur [tijdzone +0100], schreef Martin
Kratoska:
 Tlf - I believe any ideas to run it with fldigi or similar program is 
 meaningless until the principal bugs became fixed. See here:
 
 http://www.ok1rr.com/tlf-bugs/index.html
 
 It is rather uneasy to say that the latest tlf 0.9.30 is more than a 
 year old (better said 1,5) and the development seems to be stopped. I 
 would appreciate if Rein would inform us about the tlf future. There is 
 not very strong need of new features (but, of course, it will be highly 
 appreciated) but a bugfix version is more than needed.
 

I would like to work on it, once I have some other things sorted out.
Problem is, Rein's code isn't very easy to read. I am not trying to
critize Rein, but I now myself how hard it is to write software which is
understandable to other people.

 My apologies for my unpleasant comments.
 

They were not unpleasant to me I liked the technical details of
compiling a kernel which can handle 60 wpm. ;-)

 73,
 Martin, OK1RR
 
 


Joop, PG4I



___
Tlf-devel mailing list
Tlf-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tlf-devel


Re: [Tlf-devel] Rig and key control

2006-12-13 Thread Joop Stakenborg
On Tue, 12 Dec 2006 21:35:14 +
[EMAIL PROTECTED] wrote:


[...]

 
 If I understand the notes in cwdaemon correctly it will default to use 
 /dev/lp0.  I believe the cwdaemon is working because the sidetone  voice 
 keyer work just fine.  If I want to change the port for cwdaemon from lp0 to 
 something else, where can I do this?  If cwdaemon defaults to lp0, the I 
 should be able to see activity on the relevant pin using a oscilloscope or 
 voltmeter when TLF is sending - yes?
 

Hi Rob,

yes, when sending dot's a blockwave should appear.
Changing the port should be easy, they are called parport0, parport1, etc on 
linux
(See 'man cwdaemon' or 'cwdaemon -h'). As the notes say: remove the lp kernel 
module
(which is used for printing) and make sure the ppdev module is loaded.

 In summary, hamlib and rig control use ttyS0 (set in the logcfg.dat file) and 
 cwdaemon will use lp0 as default - do I have this correct?  I realize these 
 can be configured to use other ports and I have read about those set-ups on 
 this list; but I am just trying to make sure I understand this set-up 
 properly.
 

The default is always parport0.
I would be interested to know if the PTT is still working, since I have
been doing lots of code changes from 0.9.2 to 0.9.4.

 
 73
 
 Rob, N6ROB
 

Regards,
Joop PG4I


___
Tlf-devel mailing list
Tlf-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tlf-devel


Re: [Tlf-devel] Re: Tlf-devel Digest, Vol 42, Issue 2

2006-12-13 Thread Joop Stakenborg
On Wed, 13 Dec 2006 12:23:06 -0800
NY6P [EMAIL PROTECTED] wrote:


 
 What if any soundcard interface are you using?  I have the 
 TS-480, which also uses a rs-232 cable to access the TTYS0 port of the 
 computer.  I have the rig control working, but have not attempted using the 
 voice keyer or morse sender since I assume I need a soundcard interface.  
 Could you explain?  Thank you.

Cwdaemon can also beep over the console, so you really don't need
a soundcard.

With the voice keyer you *do* need a soundcard

 -- 
 
 Lee NY6P
 
 

Joop, PG4I


___
Tlf-devel mailing list
Tlf-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tlf-devel


Re: [Tlf-devel] cwdaemon on debian

2006-11-10 Thread Joop Stakenborg
On Thu, 09 Nov 2006 14:40:53 -0500
Christopher Moore [EMAIL PROTECTED] wrote:

 Hello,
 I'm running Debian unstable and get the following error when I run
 cwdaemon status
 ppdev0: failed to register device!
 

Does your parallel port work okay with a printer?
Try removing the lp module (rmmod lp) and adding ppdev (insmod ppdev).

 I'm trying to use the parallel port.  Would it be better to use a com 
 port?
 
 Thanks
 Chris w1gm
 
 

Joop, PG4I


___
Tlf-devel mailing list
Tlf-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tlf-devel


Re: [Tlf-devel] It did never work

2006-06-16 Thread Joop Stakenborg
On Fri, 16 Jun 2006 15:38:19 +0200
Martin Kratoska [EMAIL PROTECTED] wrote:

 Honestly said, xtlf never did work in my Slackware 10.2. I am getting 
 the annoying message:
 
 Can't locate Gtk2.pm in @INC (@INC contains: 
 /usr/lib/perl5/5.8.8/i486-linux /usr/lib/perl5/5.8.8 
 /usr/lib/perl5/site_perl/5.8.8/i486-linux /usr/lib/perl5/site_perl/5.8.8 
 /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_perl .) at 
 /usr/share/xtlf/xtlf.pl line 27.
 BEGIN failed--compilation aborted at /usr/share/xtlf/xtlf.pl line 27.
 

Martin,

please install libgtk2-perl. It should be available for your distribution...

 which appears with any attempt to start xtlf (any version). Played a 
 minute with cpan, no improvement. I am probably not patient enough to 
 track it down and make a fix.
 
 73,
 Martin, OK1RR
 

Regards,
Joop


___
Tlf-devel mailing list
Tlf-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tlf-devel


Re: [Tlf-devel] new beta available

2006-06-16 Thread Joop Stakenborg
On Fri, 16 Jun 2006 13:39:12 +0200
Rein Couperus PA0R [EMAIL PROTECTED] wrote:

 * I have done some work on the GUI, to include Joop's suggestions.
 

Thanks, much better now!
Debian package at http://www.xs4all.nl/~pa4tu/tmp/xtlf_0.0+1.03beta-1_all.deb

 
 73,
 
 Rein PA0R
 

Joop


___
Tlf-devel mailing list
Tlf-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tlf-devel


Re: [Tlf-devel] Xtlf-1.0.2beta is out, now incl. the iaru hf test

2006-06-12 Thread Joop Stakenborg

 The frequency in the main log is secondary (tertiary) information, which
 is only interesting for making the adif and cabrillo logs, not for
 viewing during contesting... I will follow your suggestion anyway.

Okay, understood...
BTW, if needed you can download the Debian package from
http://www.xs4all.nl/~pa4tu/tmp/xtlf_0.0+1.02beta_all.deb

Looks like xtlf is about 2 weeks away from getting accepted in Debian:
http://ftp-master.debian.org/new.html


 73, Rein




Regards,
Joop



___
Tlf-devel mailing list
Tlf-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tlf-devel


Re: [Tlf-devel] Xtlf-1.0.2beta is out, now incl. the iaru hf test

2006-06-11 Thread Joop Stakenborg
On Fri, 09 Jun 2006 14:12:43 +0200
Rein Couperus PA0R [EMAIL PROTECTED] wrote:

 I have repackaged Xtlf into 1 package, I think that is easier for the
 maintainers of various distro's.
 


Thanks Rein!
Changes needed for the Debian package:

on startup I see errors:
(xtlf.pl:15493): libglade-WARNING **: Error loading image: Openen van bestand 
'/usr/share/xtlf/./pixmaps/xtlf.png' mislukt: Onbekend bestand of map

This pixmap location seems awkward to me. /usr/share/pixmaps is the preferred 
directory for pixmaps...

Some comments on the GUI:
- the main log doesn't seem to fit the main window when started, to see 
frequency information I have to make the window wider. When I do this, the 
logwindow and buttons scale correctly, but the command line, 2 top windows and 
statusbar don't. You can fix this by removing the size limits of some of the 
widgets and enabling expand and fill. callentry, scrolledwindow2 and statusbar 
widgets seem like good candidates to do this...
- cw speed numbers don't fit in the tiny box.
- the text next to the checkbox in the Log files window don't fit.
- the text on the test button of the TRX control window don't fit.



 Hope you like it, 
 

Thanks for the effort!

 73,
 
 Rein PA0R
 

Joop, PG4I


___
Tlf-devel mailing list
Tlf-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tlf-devel


Re: [Tlf-devel] Xtlf-1.0.1beta is avalable

2006-05-23 Thread Joop Stakenborg
On Tue, 23 May 2006 16:52:07 -0400
Ed [EMAIL PROTECTED] wrote:

 
 
 Joop, this is what I get using the .deb pkg.
 
  autek:/home/ed# exit
  [EMAIL PROTECTED]:~$ xtlf
  Initializing the libraries
  Getting the GUI
  Initializing
  Filling hash table
  Initializing countries
  Show windows
  Start cluster thread
  Start gmfsk thread
  Start main loop
  Gdk-CRITICAL **: gdk_window_invalidate_rect: assertion `window != NULL' 
  failed at /usr/share/xtlf/xtlf.pl line 1734.
  Gdk-CRITICAL **: gdk_window_invalidate_rect: assertion `window != NULL' 
  failed at /usr/share/xtlf/xtlf.pl line 1734.
  Gtk-CRITICAL **: gtk_paint_box: assertion `style-depth == 
  gdk_drawable_get_depth (window)' failed at /usr/share/xtlf/xtlf.pl line 
  1589.
  [EMAIL PROTECTED]:~$

On Debian/Unstable I see:
Gtk-CRITICAL **: gtk_paint_box: assertion `style-depth == 
gdk_drawable_get_depth (window)' failed at /usr/share/xtlf/xtlf.pl line 1589.

 
 This is on an IBM A20M laptop with Debian testing. I plan on using xTLF 
 for RTTY contesting. I notice the GUI and windows as well as the overall 
 performance to be jerky for lack of a better word. There is a 
 noticeable lag before a window opens or a function executes. Am I 
 missing a needed package ??

No, you don't. As explained by Rein in an earlier message, xtlf takes about 10 
seconds to start on his machine. I think this is mainly caused by the use if 
Perl. Perl being an interpreted language, it just isn't very fast.

I am using a 700 MHz AMD, xtlf takes 15 seconds to load...

 
 Ed W3NR
 

Regards,
Joop PG4I


___
Tlf-devel mailing list
Tlf-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tlf-devel


Re: [Tlf-devel] Xtlf-1.0.1beta is avalable

2006-05-22 Thread Joop Stakenborg
On Sat, 20 May 2006 18:02:10 +0200
Rein Couperus PA0R [EMAIL PROTECTED] wrote:

 Get the bits at http://www.pskmail.org/Xtlf/
 

Preliminary Debian packages at:
http://www.xs4all.nl/~pa4tu/tmp/xtlf_0.0+1.01beta-1_all.deb

 I have done some small changes to the GUI (it looks o.k. now also under
 Dapper) and killed some error messages.
 

I have tried to create a multi-user package on Debian. Changes needed:
- config included in the package, directory: /usr/share/xtlf/config
- scoring directory is in /usr/share/xtlf/scoring
- xtlf.pl, glade file and libraries installed in /usr/share/xtlf
- /usr/bin/xtlf is a script which copies /usr/share/xtlf/scoring to 
$(HOME)/xtlf it also copies /usr/share/xtlf/scoring to $(HOME)/.xtlf and calls 
/usr/share/xtlf/xtlf.pl

Changes needed in xtlf.pl:
Line added with: use lib $Bin;, otherwise it can't find tlf_lib.pm
I have used my $contestinfo = `cat /usr/share/xtlf/scoring/rules.pm`;
also: my $g = Gtk2::GladeXML-new(/usr/share/xtlf/xtlf-1.0.0.glade);

TODO:
See if we really need to copy the scoring directory to $HOME

Feedback welcome!

 The WPX should be ok, single OP only...
 
 See you all in the WPX, I will be at DQ2006L.
 (
 http://www.l03.de/fotos/gahlen2004/index.html
 )
 
 CU next weekend!!
 
 73,
 
 Rein PA0R
 
 


Regards,
Joop PG4I


___
Tlf-devel mailing list
Tlf-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tlf-devel


[Tlf-devel] cwdaemon 0.9.4beta1 abailable for testing

2006-04-17 Thread Joop Stakenborg
Hoping to reach the right people, especially those who run *BSD...

I have just uploaded a beta version of cwdaemon to
http://www.xs4all.nl/~pa4tu/tmp/cwdaemon-0.9.4beta1.tar.gz

From the ChangeLog:
* Patch by Lada, OK1ZIA which adds threading to cwdaemon. A separate
  thread has been added for reading data from the socket. The gives us
  the advantage that cwdaemon will stop immediately after receiving ESC0
  and will not finish the current character.

Tested okay on i386 architecture. What about FreeBSD, OpenBSD 
Also, if you want to add something to cwdaemon before the next release,
this is the time to do so... :)

Regards,
Joop PG4I




___
Tlf-devel mailing list
Tlf-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tlf-devel


[Tlf-devel] colrdx

2005-08-23 Thread Joop Stakenborg
I have just released colrdx, a simple ncurses-based dx cluster client.
URL: http://pg4i.mattsnetwork.co.uk/linux/colrdx.html

Regards,
Joop PG4I
-- 
Linux for your hamradio desktop
___
 http://www.qsl.net/pg4i/linux



___
Tlf-devel mailing list
Tlf-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tlf-devel


Re: [Tlf-devel] tlf on Fedora Core 4

2005-07-14 Thread Joop Stakenborg

 HAMLIB definedSegmentation fault


 I get the segfault whether hamlib is enabled or not.  Any ideas?


Maybe recompile hamlib on your new box?

 Ben
 - --
 Ben Coleman [EMAIL PROTECTED]
  I love the way Microsoft follows standards.  In much the
 same manner that fish follow migrating caribou.
 Paul Tomblin


regards,
Joop



___
Tlf-devel mailing list
Tlf-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tlf-devel