Hello,
I wanted to release new version today but there is a problem with bug in new Freepascal compiler used in Ubuntu 13.10, Arch Linux, Gentoo, Debian unstable etc. This bug is critical and CQRLOG won't run. Problem is in CQRLOG's bandmap function that uses something new FPC compiler doesn't like. Development of new band map will take some time. I suppose new version will be released next Sunday. I'm sorry.
73 Petr, OK2CQR
Hi Petr,
Again congratulations ov a very good release. It installed with no problems and all features seem to be working properly although I have not fully tested yet so cannot guarantee there are no regression bugs hi.
I notice that on the Grayline window there is the word "Disconnected" in the left hand side of the lower status bar. I am not sure what that means?
If I have a qso and complete the log to the point where I have filled in the RST and discover that I recorded a letter wrong in the callsign and change it, the lookup information for the previous call remains. I think it would be a good idea to do the lookup again if the call is edited.
Again thank you and Martin for bringing such a great log program to us all.
73, Graeme ZL2APV
Graeme, For the greyline window,,open preferances, go to RBN and enter your info, and then the display will read connected.
I entered:
K8WDX then watch for K8WDX we will see what happens, check the box that says open when log started. I think it works in CW and digital modes, but this should show the stations that can hear you on the revers bacon network. check this site for more info. http://www.reversebeacon.net/ HTH Tom K8WDX
Tom K8WDX
Don't put any call into the watch for box, and the spots will all show on the map, you have to read more about it at the web site I posted. de K8WDX
Tom K8WDX
Hi Tom,
Thanks for the tutorial. Got it sorted now and it is really good. I was not an rbn user before but that will change now. I sure racked up a lot of QSO's this afternoon and got Jordan which I wanted.
73 Graeme, ZL2APV
Hi there, strange things occurs here.
I have typed the call sign of the station worked and focus on another field.
If I go back to the callsign field to correct one or more letters, others fields like name, QTH, grid, ITU, WAZ don't update regarding the new call typed, and the new info from the Callbook base are added after the ones of the previous callsign.
73 Denis FO5MD
The best way to correct a call is to hit the Esc key 2 times, this will clear the qso, and then just renter the call, hit tab and the correct info should be there... HTH
Tom K8WDX
Hi Tom, thank you for your reply.
OK "brute force" is an available option and THE way to go if you want to change the call and to record a new QSO. If the purpose is to correct a single letter I think that way not appropriate because then I'll be forced to re-enter the fields that I typed and that I would like to keep unchanged but which have been deleted while a single letter of the call is incorrect. Being myself programmer I would propose rather not to change fields that have been filled from the keyboard input but only those who have been automatically populated.
Anyway this is not critical, just a little annoying.
73 Denis FO5MD
Hi Denis and Tom,
I think that already if you have data in the field or it has been filled with data from a previous QSO, the lookup only fills empty fields so that part is already there. The problem is that editing a letter does not redo the lookup. I agree that if you have already filled in data and you erase the qso it is not always possible to remember what you had entered and if the station is gone or started another qso it is lost. Maybe I should improve my CW so I don't get calls wrong in the first place hi.
73 Graeme ZL2APV
This is kinda a pain, and I know what Denis is talking about, this is bad when you get a pile up, when I get on 80M or 40M and call CQ this generates a pile up, mostly on 80M from Europe, and sometimes you don't get the call just right and when you correct a missing or incorrect letter, the info does not update, would be nice that after a letter or # change in the call field, if I hit tab then the info would update to the change, but it does not, so what I do is just hit the Esc 2 times fast and start all over, This creates a new problem, my memory is not that good anymore hi hi, and then the opportunity to really mess up the call presents itself. and when I am trying log qso's fast, messing up calls happens frequently. So the pad with the pen is sitting right next to me, and when conditions are tough, I will write them down till I get them right, seems to work ok.....
Tom K8WDX
Fixing this will be quite tricky and there is more to do than superficially apparent.
When an edit occurs on the call field ...
1. All filled fields will need to be checked against the original faulty call and deleted if they match. This will retain any fields you have entered data into. This means that the original entered call needs a buffer so it can be retrieved.
2. The new call will need to be looked up and any empty fields will need to be filled with data from the lookup.
A bit messy but would work. Here in ZL I tend to have pile-ups on my call and trying to get a call correctly through the QRM is very difficult so I run into the problem often. CQRLog behaved this way in previous versions so it is not a regression.
73 Graeme ZL2APV