Re: [Klog-users] Features needed..

[Jaime Robles]

Good morning,
I will answer between your lines...

> I'm trying 0.4.3 and imported a large log of over 12,000 QSO's. I noticed
> that some of the log entry details are NOT shown in the log section,
> like name, locator, QSL sent/received. These details can only be seen
> when you do a SEARCH for a particular callsign. Maybe the font of the
> log section is too big, and I cannot show all the fields.
I think that may be the problem, the fonts.
If you check the following screenshot:
http://jaime.robles.es/klog/imagen/klog-040sorting.png

you will see that the name and locator is shown in the QSO/main tab for a
QSO.
It is not shown in the log tab... as I choosed not to do it. I thought
that showing all the data in the log would not be confortable. The way to
see all the data for one QSO is to "edit" (double-click) it. If you edit a
QSO, all the data for that QSO is shown in the edit tab.


> It would be nice to be able to show the DXCC or WAZ total for each BAND or
> MODE, and to able to edit the DXCC or WAZ file from within the program,
> as for example the WAZ is not always entered correctly from the log.
Zone, continent, entity name and some others comes from the CTY.DAT file.
CTY.DAT file.

> Try entering UA0Y and you will see the ZONE is wrong in the INFO section.
> Of course, UA0Y is zone 23.
The best way to proceed with that, I think it is informing James
(http://www.country-files.com) about this issue on the call UA0Y.
I will CC him this email and ask him to fix that. He usually answer fast! ;-)

> You need a ZONE field within the log input
> as well, so when you enter the callsign in the log, it will always be
> correct.
I could do it, of course... maybe a zone input box... the main problem
with this is that this box would be usually left blank as the cty.dat file
is usually accurate for the most of the calls and the box would be usefull
just for a minimum number of calls... Any idea on this?


> You also need a DXCC field for the log input, as sometimes it will not be
> correct from CTY.DAT. for example EA2BB/LH is shown as NORWAY, but if
> there was a DXCC field, you could enter the correct DXCC entity.
And.. if EA2BB/LH is not norway... what is it? A lighthouse??

Maybe I could add the "/LH" to the group of "special prefixes" like "/P,
/J, /M, /MM, ..." so it does not affect to the DXCC entity of the main
QRZ.
That way, EA2BB/LH would be Spain, EA and not Norway.

Would it be ok?

-- 
Un saludo,
        Jaime Robles, EA4TV
        address@hidden

Visita:
   http://jaime.robles.es