I ran into a similar situation with the following message:
CQ NO3M DXto keep stateside callers from answering. I had assumed the "CQ" would have been picked up and TX Enable persist after each invocation. However, that was not the case. I saw other DX stations at the time using the same format of message and wonder how they are doing so without re-enabling the Enable TX each time; perhaps something JT-Alert does for them? Of course, JT-Alert is not able to run on *nix, so that's not an option here.
It would be nice to be able to send a "recognized" CQ that will keep the locals from dampening a DX "run".
73 Eric NO3M On 03/05/2015 04:04 PM, Guy wrote:
I am not a programmer at all, but I do follow this list and find what I read fascinating even though I don't understand it. I currently use the 1.3 release and it has a behaviour that I find annoying and I wonder if it has been addressed in either 1.4 or 1.5. When sending a custom CQ call, the 'enable tx' goes off after the first call and one has to continually press i carry on sending the custom CQ. I'm like it to stay on as it does for the standard CQ call. Thanks.
------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
