Re: [Tlf-devel] TLF Bugs

2016-11-19 Thread 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 :

> 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 :
> 
> > 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


Re: [Tlf-devel] TLF Bugs

2016-11-14 Thread Thomas Beierlein
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 :

> 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


Re: [Tlf-devel] TLF Bugs

2016-11-13 Thread Fred Siegmund
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




___
Tlf-devel mailing list
Tlf-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tlf-devel


Re: [Tlf-devel] TLF Bugs

2016-11-13 Thread Thomas Beierlein
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 
> Enter (wkd in previous versions)

Ok. I will check.

> 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


Re: [Tlf-devel] TLF Bugs

2016-11-01 Thread Thomas Beierlein
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
> 
Fixed code pushed to master branch. A maintenance release 1.2.4.4 will
follow shortly.

73, de Tom

> 
> Am Sun, 16 Oct 2016 09:53:00 +0200
> schrieb Thomas Beierlein :
> 
> > 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 coming home from a business trip.
> > 
> > Thanks for pointing out the problem. For now setting BMAUTOGRAB in
> > logcfg.dat should help.
> > 
> > 73, Tom DL1JBE
> >   
> > > When using a initial_exchange file it would be better, if it is in
> > > place to show just somewhere the exchange and not to put it in the
> > > exchange field. Because like in WAG you are getting DOKs and
> > > serial numbers and with RECALL_MULTS it shows also the serial
> > > numbers (which you don't want).
> > > 
> > > 73 Fred
> > > 
> > > ___
> > > Tlf-devel mailing list
> > > Tlf-devel@nongnu.org
> > > https://lists.nongnu.org/mailman/listinfo/tlf-devel
> > 
> > 
> >   
> 
> 
> 



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


___
Tlf-devel mailing list
Tlf-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tlf-devel


Re: [Tlf-devel] TLF Bugs

2016-10-26 Thread FS

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 DL1JBE


Am Sun, 16 Oct 2016 09:53:00 +0200
schrieb Thomas Beierlein :


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 coming home from a business trip.

Thanks for pointing out the problem. For now setting BMAUTOGRAB in
logcfg.dat should help.

73, Tom DL1JBE


When using a initial_exchange file it would be better, if it is in
place to show just somewhere the exchange and not to put it in the
exchange field. Because like in WAG you are getting DOKs and serial
numbers and with RECALL_MULTS it shows also the serial numbers
(which you don't want).

73 Fred

___
Tlf-devel mailing list
Tlf-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tlf-devel










___
Tlf-devel mailing list
Tlf-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tlf-devel


Re: [Tlf-devel] TLF Bugs

2016-10-16 Thread Thomas Beierlein
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 coming home from a business trip.

Thanks for pointing out the problem. For now setting BMAUTOGRAB in
logcfg.dat should help.

73, Tom DL1JBE

> When using a initial_exchange file it would be better, if it is in
> place to show just somewhere the exchange and not to put it in the
> exchange field. Because like in WAG you are getting DOKs and serial
> numbers and with RECALL_MULTS it shows also the serial numbers (which
> you don't want).
> 
> 73 Fred
> 
> ___
> Tlf-devel mailing list
> Tlf-devel@nongnu.org
> https://lists.nongnu.org/mailman/listinfo/tlf-devel



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


___
Tlf-devel mailing list
Tlf-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tlf-devel


[Tlf-devel] TLF Bugs

2016-10-15 Thread 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?


When using a initial_exchange file it would be better, if it is in place 
to show just somewhere the exchange and not to put it in the exchange 
field. Because like in WAG you are getting DOKs and serial numbers and 
with RECALL_MULTS it shows also the serial numbers (which you don't want).


73 Fred

___
Tlf-devel mailing list
Tlf-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tlf-devel


[Tlf-devel] tlf bugs update

2007-04-24 Thread Martin Kratoska

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.


more details:
http://www.ok1rr.com/tlf-bugs/index.html

(not public, it is a hidden link)

I hope that our beloved tlf is not abandoned (last version is more than 
1 year old...).


73,
Martin, OK1RR


___
Tlf-devel mailing list
Tlf-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tlf-devel