[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Tlf-devel] TLF 1.1.0

From: Thomas Beierlein
Subject: Re: [Tlf-devel] TLF 1.1.0
Date: Tue, 6 Sep 2011 19:31:55 +0200

Hi Graham,

thanks for the report. Let me give some comments.

Am Fri, 2 Sep 2011 14:42:17 -0400
schrieb "Collins, Graham" <address@hidden>:

> I use Ubuntu 10.04lts and initially had problems with TLF 0.9.x and
> was never able to run the app but what I read about TLF intrigued me
> and I eventually found the fix and the more recent versions 1.x.x.
Well, the TLF 0.9 series got crippled by the fact that newer glibc
libraries do not tolerate buffer overflows anymore. That was one of the
main reasons to do a TLf 1.0 release.

> So far so good. I created a rules file for use in the Ohio QSO party
> last weekend and I am quite pleased with TLF and it is suitable
> substitute for N1MM for my needs.
> The only issue I had with TLF was when I created the Cabrillo log,
> TLF truncated the exchange field. The exchange for the QSO party was
> the four letter abbreviation for the county (i.e. LAKE). This filed
> was truncated to either two or three characters dependent on one of
> the other data fields. The full four characters where in the TLF log
> so it looks like it is just a simple truncation issue. I may just
> take some time to write a little program to convert the TLF log to
> Cabrillo.
One problem are the different cabrillo formats for different contests.
TLF supports only one or two basic formats (WPX if I remember correct).

For the moment I also would suggest an external conversion (maybe by
some AWK magic). If you find a working solution, let us know. I can add
it to the next versions so others can benefit from it.

> Someone else mentioned that they desired to have the frequency
> logged. This is also one of my desires. The data is available through
> hamlib and displayed and in QSO mode (i.e. not Contest mode) the
> frequency is put in the TLF log (as the last entry on the line I
> think). 
That is on the TODO list for next time. But it will request a cmplete
change of the log file format. In dxcc mode there is room in the 80
character log lines, but not in contest mode. So for that to solve we
need to switch to another log format.

> I have started to look through the source code to try and get a
> better understanding of how the program works and what would be
> required to add the frequency to the TLF log in contest mode.
Think also, that you need to reread the data in case you stop and later
restart TLF.

Let us know if you find some way to do it.

73, de Tom DL1JBE.

> Cheers, Graham ve3gtc
> -----Original Message-----
> From: address@hidden
> [mailto:address@hidden On Behalf
> Of Thomas Beierlein Sent: September 2, 2011 01:09 To:
> address@hidden Subject: Re: [Tlf-devel] TLF 1.1.0
> Hi Fred,
> back from holiday let me answer your test report. 
> First thanks for the report.
> Am Mon, 08 Aug 2011 23:11:59 +0200
> schrieb Fred Siegmund <address@hidden>:
> > first: I had a very good time in EUHFC with the programme although 
> > coming from a CT-based logger like yfktest
> > is something new to learn. Especially with "SPACE" to transmit
> > something is unusal. I don't know which use-case
> > that is for. I often trx'd my call at the wrong time because I
> > pressed "SPACE" intuitivly to go to the numbers field. :-)
> Better use 'ENTER' to switch from one QSO state to the next (including
> sending).
> >   Bandmap works great. Maybe the combination "CTRL-G" is not the
> > best choice because the G is so far away
> > on the keyboard for one hand maybe "CTRL->" and "CTRL-<" to go
> > downwards in frequency would be a better choice but
> > thats my personal feeling. 
> I kept CTRL-G as it was used in the former - very limited - bandmap
> display and did not want to irritate long time TLF users with a new
> key combination. But CTRL-< sounds like an alternative for the future.
> > Some more notices:
> > 
> > - "segmentation fault"
> > If the number of spots is >200 its likely the programme crashes
> > soon with this announcement.
> Thanks for reporting. I will look into this.
> > 
> > - life time for spots
> > When using reversebeacon the bandmap is soon very crowded. And
> > because the skimmers set a new spot every 15min
> > or so, its not neccessary to keep them for a longer time in the
> > bandmap then that.
> > 
> OK. It will be user adaptable in the future.
> > - exact frequency in cabrillo
> > More and more contests sponsors require the exact frequency named in
> > the cabrillo file for extended checking.
> > 
> I know, but that is a lot of work in TLF as a whole. Thanks for
> reminding me.
> > - graphics/terminal related
> > Beside the known colour problems, in my xterm the complete lower
> > half is now band map, means "MEM" frequency
> > display and country information (green bar at the bottom) is gone. 
> > Probably terminal related.
> > 
> First the colour problem: You can define the 16 colors which xterm
> uses in your ~/.Xdefault and restart X or 'xrdb .Xdefault', e.g.:
> *color0:  #000000
> *color8:  #555753
> ! DarkRed + Red
> *color1:  #ff6565
> *color9:  #ff8d8d
> ! DarkGreen + Green
> *color2:  #93d44f
> *color10: #c8e7a8
> ....
> Regards 'MEM' display and bottom bar - that is respected for me. Any
> other station can confirm this?
> > - .paras file
> > I changed the messages F1-F6 for my personal needs but if I edit
> > the write-out in .paras for the top green bar, it doesn't show up
> > in the programme.
> > 
> The .paras file is not really used - I do not know if it was ever.
> Please use the logcfg.dat for setting your messages. But the displayed
> top bar is a fixed text (as it seems it was from the beginning).
> Changign that bar according to your CW messages is already on the todo
> list.
> 73, de Tom DL1JBE.

"Do what is needful!"
Ursula LeGuin: Earthsea

reply via email to

[Prev in Thread] Current Thread [Next in Thread]