Have had the issue on Ipad where the call lookup is pulling info on a truncated portion of the call occasionally. It seems to happen more when I’m operating fast (200 q/h).
For example, I worked KJ5GGT, but in my log it pulled ithe info for KJ5GG
Have had the issue on Ipad where the call lookup is pulling info on a truncated portion of the call occasionally. It seems to happen more when I’m operating fast (200 q/h).
For example, I worked KJ5GGT, but in my log it pulled ithe info for KJ5GG
What version was this issue on @ww8l? The latest November release (in testing; should be out very soon) contains some bug fixes and performance improvements that may resolve this.
This was a persistent issue for me for quite a while but it has been fixed (for me) since the October release. I have not experienced this with November also.
Just confirm your version?
Alan
One more thing to remember, you cannot avoid the latency of a lookup to QRZ. It takes time to actually retrieve the data. So if you cannot stop long enough for the last letter input to make this request, there is always (now at least) the action of bulk lookup off the dot menu:
I also have a callsign names (notes) lookup file installed (77k names) which is offline and is more immediate for lookups. I can send and move on without worrying too much about the lookup not being correct. Then later I can do the bulk lookup to fix any suspected errors.