Re: [Tlf-devel] TLF Bugs

[Thomas Beierlein]

Both reported bugs are fixed in TLF-1.2.4.4.
Be aware that there may still be a problem with BMAUTOGRAB if spot are
really near by another. It is on the To-do list, but first I will
integrate the native fldigi interface which Ervin provided some
times ago.

73, de Tom DL1JBE

Am Mon, 14 Nov 2016 20:29:34 +0100 schrieb Thomas
Beierlein <address@hidden>:

> I could reproduce the bug and found the reason. There is a 100 hz
> tolerance for evaluating the rig frequency and finding the according
> spot to show. It is a classical border problem where a <= was needed
> and only a < got implemented.
> 
> The fix is easy but there showed up another problem related to the
> BMAUTOGRAB feature (especially when you turn away from the frequency
> to the near neighbor spot). We need to find a solution for that too.
> 
> More information later.
> 
> 73, de Tom DL1JBE.
> 
> 
> Am Mon, 14 Nov 2016
> 08:28:06 +0100 schrieb Fred Siegmund <address@hidden>:
> 
> > The bandmapdisplay does not follow CTRL-G to the actual call.
> > Instead it jumpes to the next 100Hz further spaced call. If you
> > have some calls that are 100Hz spaced from reversebeacon you can
> > see this behaviour. Might be difficult to see outside the big
> > contests.
> > 
> > 73 Fred
> > 
> > Am 14.11.2016 um 07:08 schrieb Thomas Beierlein:
> >   
> > >> 2. the bandmap display shows the wrong call, if 2 Calls are only
> > >> 100Hz spaced from each other after arriving with CTRL-G (Call in
> > >> call input field is ok)
> > >>    
> > > Can you give an example and show what is right and wrong please.
> > >
> > > Thanks and 73, de Tom
> > >
> > >    
> 
> 
> 



-- 
"Do what is needful!"
Ursula LeGuin: Earthsea
--