Re: [Wsjt-devel] DXCC entity and worked B4 status

[Laurie V. <vk3...@gm...>]

Murray,

I suggest you test against a large (several thousand entry) adi file. 
Once the file gets large and with many decodes to process at the end of 
the RX cycle you will experience performance degradation due to 
searching against a two non-indexed flatfiles (cty.dat and log.adi) for 
each callsign.

de Laurie, VK3AMA
------------------------------------------------------------------------

On 31/07/2013 9:41 PM, Murray Curtis wrote:
> Hi
>
> I've just committed a first version of DXCC entity, rev 3512.
>
> This version will display the DXCC entity of a station calling CQ. 
> This is preceded by a '!' if this is not in the log or '~' if you've 
> worked this entity before but not this call.
>
> The log read is currently the wsjtx_log.adi in the install directory.  
> This will be brought up into the config (devsetup) window at some 
> point. The code is also hard coded to look for cty.dat (the DXCC data 
> file) in the same install directory.
>
> The feature is enabled/disabled in the drop down setup menu.  On 
> enable it will (re)read the log and cty.dat files and write to 
> qDebug() (stdout on Linux) a line showing the QSO and countries worked 
> counts.   It currently also writes some debug data when searching for 
> a CQ call.
>
> Its pretty simple, knows nothing of bands and only deals with JT9 and 
> JT65 modes.
>
> Feedback, good and bad is always welcome.
>
> Cheers
> Murray
> VK3ACF
>
>
>
> _______________________________________________
> Wsjt-devel mailing list
> Wsj...@li...
> https://lists.berlios.de/mailman/listinfo/wsjt-devel
>