----- Original Message -----
From: Dino <davorin.istvanovic@zg.htnet.hr>
Reply-To: <hamlogger@groups.io>
To: <hamlogger@groups.io>
Sent: 28/12/2021 12:23:57
Subject: Re: [hamlogger] slow input of callsign
________________________________________________________________________________


Hi, Ian.
Maybe we use L32 in different way.

I configured L32 for my personal needs. I have database for awards I
need ( User 1, 2 , 3).
I don't use all benefits of L32, infact, just basic... don't use direct
logging, rotator controll, RIG controll, skimmer, DX cluster etc.
For all extra I use separate software, run them separatly and all ports
are connected and controled via MicrroHam... and it is very simple and
stabile

73 Dino

On 28.12.21. 12:53, g4girhb0 via groups.io wrote:

Hello Ken,

You have found exactly what I have!! Just posted to Dino my findings.

Dino, sounds like we have been living in a parallel world!! Similar conditions
here, Would have had more QSO's in the Log if I hadn't fell prey to the fairer
Sex!!
No regrets of course.
73

Ian G4GIR



----- Original Message -----
From: <kenfilmer@outlook.com>
Reply-To: <hamlogger@groups.io>
To: <hamlogger@groups.io>
Sent: 28/12/2021 11:23:31
Subject: Re: [hamlogger] slow input of callsign


As Ian suggests the problem exists where there are lots of certain prefixes in
the log, 47,500 total in my log incidentally.

Putting a P5 in the log is immediate (not too many P5s in the log).
Putting a German call, gets to DL then the wait symbol, 3 secs wait, , about
600 D calls in my log
Russian calls the R is immediate then 6 secs wait, same with U, 5 secs wait, .
about 6,500 R calls in log, 1.200 U calls.
K and W are almost immediate, 1 sec wait, although I have lots of US,
probably due to numerous different prefixes.

Hardly a definitive analysis but it appears that the more of a certain prefix
there is in the log, the longer it takes to enter the call in the logging
window.

My PC has a HDD, W10 Professional, I forget what the spec is, don't know how to find out.

Ken G3XPO