Re: [Tlf-devel] New TLF prelease tlf-1.1pre1

[Thomas Beierlein]

Hi Fred, hi Andy,

just got time to look into it:

1. VKSPR and VKCWR are badly named. THey should be VKSPM (S&P message)
and VKCQM (CQ message). I will rename it in next prerelease accordingto
the manual.

2. In SSB mode pressing enter log the QSO immediately without any
following messages. 
Before tlf-0.9.23 it sent the VKSPM or VKCQM. That got changed by Rein
with that version. I do not know why! But we can revert the change in a
very simple way. If you do not define the filename in logcfg.dat it
will not send anything. So you can decide on your own how you like it.

What do you think?

73, de Tom DL1JBE.

Am Wed, 26 Oct 2011 21:24:12 +0100 schrieb Andy
Summers <address@hidden>:

> Hi again Fred,
> 
> I've had a look but I haven't really got to the bottom of it.
> According to the most recent manual this recording is VKSPM, not
> VKSPR, despite "parse_logcfg.c" apparently looking for VKSPR.
> 
> The auto exchange behaviour is actually contained in "logit.c". In
> there you'll see that 'ph_message[12]' is to be played in S+P mode.
> That message is recorded via "audio.c" on the 'S' message.
> Unfortunately, if you try to record to 'S' there is a problem.
> However, I recorded a message on another F-key and manually renamed
> it to "vkspm.wav". In the rule file I added
> "VKSPM=/home/ags/tlf/vkspm.wav", and this actually worked! I tried
> the same with the VKCQM message, but then it all stopped working. In
> any case, it looks like CQ mode doesn't send the VKCQM message but
> the F3 message anyway.
> 
> If you really want the VKSPM function for the weekend you could try
> this work-around. In slow-time we have to work out what's the
> underlying problem.
> 
> 73 Andy, G4KNO.
> 
> On 26/10/11 10:16, FS wrote:
> > Hi all,
> >
> > while preparing for WWDX SSB I noticed that the VKSPR message is
> > not sent in SP mode after inserting the zone in the numbers field.
> > The Call file is sent after inserting the other stations call at
> > "call input". Anybody knows why? I saw a lot of g4kno editing in
> > the sources there ;-)
> >
> > 73 Fred
> >
> > On 10/25/2011 04:32 AM, Thomas Beierlein wrote:
> >> Hi Andy,
> >>
> >> thanks for your test report. Let me try to answer your questions.
> >>
> >> Am Mon, 24 Oct 2011 20:25:10 +0100
> >> schrieb Andy Summers<address@hidden>:
> >>> Thanks for the new bandmap functions. I've been trying it out
> >>> with a view to dabbling in CQWW - I'm aware it may not be stable.
> >>>
> >> I did some work in last weeks to  stabilize it and I think pre2
> >> will be much better there.
> >>
> >>> I've read the New_Bandmap.txt and don't think it works as
> >>> described there. If I enter a call, press ctrl-A, I see it added
> >>> to the bandmap. I tune somewhere else and do the same thing. I
> >>> can do this several times and see the calls added, but when I
> >>> repeatedly hit ctrl-g it only picks the most recent spot.
> >>
> >> You are right, that is what is implemented. My idea behind that was
> >> that you normally only have one spot of a station per band and
> >> mode. If you filter your bandmap by mode or band Ctrl-g will
> >> select the right spot.
> >>
> >> Are there reasonable scenarios where we have would need to select
> >> between more than one spot per band/mode for the same station?
> >> Than I should think about a way to handle it.
> >>>
> >>> Also, I see that a MEM frequency appears under the normal
> >>> frequency display, but you don't say how to get the rig back onto
> >>> that frequency. Simply switching mode back to Log, doesn't do it.
> >>>
> >> The memory recall is the same as in normal memory operation. As
> >> the man page says hitting '#' records frequency if memory is empty
> >> and recalls it if it is set. So after grabing a spot you can
> >> switch back to Run mode by '+' and to old frequency by '#'.
> >>
> >>> It would be quite useful to be able to arrow up/down the spot list
> >>> and select the specific spot you want, rather than have to scroll
> >>> through the lot to get to the one you want. It's a long time
> >>> since I used CT, but it might be worth studying how that worked.
> >>> I do remember that you could toggle alt-F4 (or was it F3) to
> >>> toggle between the selected spot and the current run frequency.
> >>> That was really useful for continuing to CQ, keep your frequency
> >>> warm and periodically check back to see if the spot was workable.
> >>>
> >> I see the point and will think about to implement something
> >> similar. But it will be at low priority at the moment.
> >>
> >>> BTW, the score or frequency window overlaps the new spot mode info
> >>> and doesn't look right.
> >>>
> >> The score window will be in the upper right in next prerelase
> >> (just did it yesterday :-) ). As the frequency window is only
> >> temporarily visible it may hide the bandmap for that time - should
> >> be acceptable.
> >>
> >> Am Mon, 24 Oct 2011 20:28:04 +0100
> >> schrieb Andy Summers<address@hidden>:
> >>
> >>> I also forgot to mention that if you log a call but then hit
> >>> minus to delete the last QSO, that call shows up in the bandmap
> >>> as a dupe.
> >>>
> >> Same as for correcting the score after delete, see below...
> >>
> >>> On 07/10/11 18:54, Thomas Beierlein wrote:
> >>>>     !!! If you delete a QSO you have to manually rescore the log
> >>>> (:res).
> >>>>
> >>
> >> Btw, I plan to release the next prerelease version in next two
> >> week.
> >>
> >> 73, de Tom DL1JBE.
> >>
> >
> > _______________________________________________
> > Tlf-devel mailing list
> > address@hidden
> > https://lists.nongnu.org/mailman/listinfo/tlf-devel
> 
> 
> _______________________________________________
> Tlf-devel mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/tlf-devel



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