Hi Fred, Since you mentioned me...
It is true that I messed around with that code. The code used deprecated sox arguments, so the voice keyer was broken for recent versions of sox. I fixed this, changed the record function to terminate with <ESC> rather than ctrl-c, and added an ALSA mute function so that sound cards could be used without the need to physically switch the mic (i.e. like N1MM). As far as I am aware I haven't altered the function of VKSPR, but I'll have a look when I get home tonight. I've never used VKSPR, preferring to hit the F-keys instead. I think it's highly unlikely you'll see a fix for this before CQWW though! 73 Andy, G4KNO. On Wed, Oct 26, 2011 at 10:16 AM, FS <dh...@freenet.de> 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<g4kno.m...@gmail.com>: >> >>> 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<g4kno.m...@gmail.com>: >> >> 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 > Tlf-devel@nongnu.org > https://lists.nongnu.org/**mailman/listinfo/tlf-devel<https://lists.nongnu.org/mailman/listinfo/tlf-devel> >
_______________________________________________ Tlf-devel mailing list Tlf-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tlf-devel
