[WT-support] default.dta file

Clive Whelan clive.whelan at btinternet.com
Wed Aug 19 13:06:20 CEST 2009


No Bob, as I said previously it happens with only a single entry in the 
xdt file and is no slower with 500, so it's not a processing problem per 
se, clearly an overhead. As I also said, there is zero delay in the 
partial window to display the same information which is therefore up to 
half a second ahead of the xdt file.

At that point I run out of expertise. I have redundancy in respect of 
the display in the partial window from the default.dta file so it's not 
that big a deal in the grand scheme of things. I think I need to move on 
and get more real-world experience of the prog. and perhaps come back to 
minor problems of this kind later.

Thanks for your input.


73


Clive
GW3NJW

Bob Wilson, N6TV wrote:
> On Tue, Aug 18, 2009 at 4:25 PM, Clive Whelan 
> <clive.whelan at btinternet.com <mailto:clive.whelan at btinternet.com>> wrote:
>
>     No , in fact there is a finite delay of perhaps 300mS after the
>     callsign
>     has been entered before the name pops up
>
>
> When using an 8,000-line, 315 KB .XDT file, I detect no such delay on 
> a 2 GHz Pentium running Windows XP.  Did you say your .XDT file has 
> only 500 lines?
>
> Fom the doc: 
>    "This function is designed to work with no more than a few thousand 
> callsigns only. Don't try it with millions of lines or a Callbook file! "
>
> Make sure your .XDT file isn't filled with trailing blanks, that there 
> is one callsign per line, that there are no duplicate callsigns, and 
> that it is sorted by callsign (I don't know if the latter is required, 
> maybe it helps), and that each line ends with CR/LF instead of just CR 
> or just LF.
>
> 73,
> Bob, N6TV
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Support mailing list
> Support at win-test.com
> http://www.f5mzn.org/cgi-bin/mailman/listinfo/support
>   


More information about the Support mailing list