My apologizes for re-sending this email - pushed (or rather clicked) the wrong spont and "pooof" it was resent ;)
Cheers, Graham ve3gtc -----Original Message----- From: tlf-devel-bounces+colling=navcanada...@nongnu.org [mailto:tlf-devel-bounces+colling=navcanada...@nongnu.org] On Behalf Of Collins, Graham Sent: September 6, 2011 13:33 To: tlf-devel@nongnu.org Subject: Re: [Tlf-devel] TLF 1.1.0 Tom (and all), Glad to see that there is some work continuing on TLF. I have been a user of N1MM logger for some time and was the only reason I kept a computer that used Windows. I tried just about every program I could find for contest logging on Linux but never found suitable substitute for N1MM. 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. So far so good. I created a rules file for use in the Ohio QSO party a couple of weekends and I am quite pleased with TLF and feel it is a 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 field 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 when TLF creates the Cabrillo log. I may just take some time to write a little program to convert the TLF log to Cabrillo. Someone else mentioned that they desired to have the frequency logged. This is also one of my desires. The data is available through hamlib, is 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). 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. Cheers, Graham ve3gtc -----Original Message----- From: tlf-devel-bounces+colling=navcanada...@nongnu.org [mailto:tlf-devel-bounces+colling=navcanada...@nongnu.org] On Behalf Of Thomas Beierlein Sent: September 2, 2011 01:09 To: tlf-devel@nongnu.org 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 <dh...@freenet.de>: > 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 -- _______________________________________________ Tlf-devel mailing list Tlf-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tlf-devel _______________________________________________ Tlf-devel mailing list Tlf-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tlf-devel
