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
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 t
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
Hi,
just some questions for clarification.
Am Sun, 13 Nov 2016 11:25:20 +0100
schrieb Fred Siegmund :
> Again some problems with the master-branch:
> 1. When editing the last QSO (because exchange was wrong or so) the
> cursor does not jump to the "call input" field again after pressing
> Ente
Again some problems with the master-branch:
1. When editing the last QSO (because exchange was wrong or so) the
cursor does not jump to the "call input" field again after pressing
Enter (wkd in previous versions)
2. the bandmap display shows the wrong call, if 2 Calls are only 100Hz
spaced from
Am Wed, 26 Oct 2016 07:30:10 +0200
schrieb Thomas Beierlein :
> As a short continuation
>
> The bug was found in meantime but still needs a proper solution. I
> hope to work on it next weekend.
>
> In meantime please use the setting of BMAUTOGRAB as suggested below.
>
> 73, de Tom DL1JBE
>
Great!
Thanks,
Fred DH5FS/DM3F
On 10/26/2016 05:30 AM, Thomas Beierlein wrote:
As a short continuation
The bug was found in meantime but still needs a proper solution. I hope
to work on it next weekend.
In meantime please use the setting of BMAUTOGRAB as suggested below.
73, de Tom DL1JB
As a short continuation
The bug was found in meantime but still needs a proper solution. I hope
to work on it next weekend.
In meantime please use the setting of BMAUTOGRAB as suggested below.
73, de Tom DL1JBE
Am Sun, 16 Oct 2016 09:53:00 +0200
schrieb Thomas Beierlein :
> Am Sat, 15 Oct
Am Sat, 15 Oct 2016 15:12:31 +0200
schrieb Fred Siegmund :
> Hi, some problems with the actual master branch, found during
> preparation for the WAG contest:
> -G does not show the call anymore in the callsign field, when
> grabbing the next call > must be a bug?
>
Sorry for late reply - junst
Hi Fred,
On Sat, Oct 15, 2016 at 03:12:31PM +0200, Fred Siegmund wrote:
> Hi, some problems with the actual master branch, found during
> preparation for the WAG contest:
> -G does not show the call anymore in the callsign field, when
> grabbing the next call > must be a bug?
could you show your
Hi, some problems with the actual master branch, found during
preparation for the WAG contest:
-G does not show the call anymore in the callsign field, when
grabbing the next call > must be a bug?
When using a initial_exchange file it would be better, if it is in place
to show just somewhere t
Update Apr. 22, 2007
While operating the special call OL75CAV on 30 metres in DXpedition mode
I find another bug - all QSOs were on 30 metres exclusively but if
exiting program and restarting, all Q's counted as 40 m. New Q's counted
on 30 m until next restart, then counted as 40 m again.
mo
12 matches
Mail list logo
