Hack AA5VU has addressed the time on / time off issue more clearly than I did, so I won't go into it here, but I want to clarify about the macros.
Suppose you click or type into the TX window, even a few spaces, which are totally invisible in the TX window. (Or you run a macro that outputs spaces or something else.) Then you search & pounce but when you pounce your CW does nothing, or your RTTY sends a bunch of spaces, or worse yet, it sends the text you've accidentally pasted into the TX buffer. So I will make my contest macros do this: <CLEARTX><TX>... before they launch into the exchange, return, etc. Leigh/WA5ZNU > On 11/17/2010 01:56 PM, Leigh L. Klotz, Jr. WA5ZNU wrote: >> I reported or requested these on the devel list after operating in CW >> Sweepstakes. >> >> The log change could be addressed by export, but I noticed that the adif >> log file was storing the qso by the date you started but the time you >> ended. So if you have a qso which crosses a gmt date boundary it >> appears >> in the way wrong spot in the file. I reported to Dave that it was >> sorting >> by date on and time off. > > > I agree that needed to be fixed. But a cabrillo wants date and time off, > not on. But the ARRL has always been the odd man out. > > The saving grace is Dave allows the user to select what he wants or needs. > > Plus we have the option to edit the log. > > >> >> In a contest you probably want date on instead of date off, but as you >> all >> point our, you can handle the choice in export. No matter what the fix, >> though, date on and time off together is wrong. > > > In any contest you want date off and time off. > > > >> The clear tx macro is for use in other macros, not for use by itself. >> I >> wanted the contest macros to clear any accidental TX text before >> transmitting. The default macros CQ etc probably don't want to do this >> since people might type in som,e text and press CQ instead of CALL or >> something, but in general, I think contesters will want the macros to >> send >> exactly only the text in the macro. > > > You are correct, but any contester worth his salt, has the macros set > exactly as needed. But in the heat of battle it may come in handy. > > > >> There is another bug that exec macros are inserting spaces even if there >> is no output, but that is I believe unaddresed. >> >> Leigh/WA5ZNU >> > > > Ed W3NR > > _______________________________________________ fldigi-alpha mailing list [email protected] https://lists.berlios.de/mailman/listinfo/fldigi-alpha
