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 <dh...@freenet.de>: > 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 -- _______________________________________________ Tlf-devel mailing list Tlf-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tlf-devel
