Oops!
Posted this with wrong sender address. This should now go to list:
Sakari Nylund kirjoitti 19.03.2018 klo 20:10:
HI all!
As I said: My apologies for too fast reporting. As explained on my
2nd message it was my PTT line switched off. Sorry.
I have now written an update to cqrlog where I used that non-cq
feature and it works as expected: sets std messages, but does not fire
TX.
What Karza writes came up also to my mind:
Why double click on non-cq in "band activity" fires TX ?
It would be good that it just loads std messages. Nothing else. Or
that firing TX could be enabled or disabled in this case via
configuration, or check box.
That would make it like "single click" feature.
The update to cqrlog has no proper purpose, just tried it. I can not
figure any true need for this in external program.
Actually if I would like to produce "single click" like feature via
cqrlog I had to write a new copy of "band activity" window to it.
And that is stupid copying.
I have not used JTAlert ever (no need, I have same features in cqrlog)
but I have feeling that it collects all heard calls from band (not
just cqs) and makes "needed list" from them. I that case there is need
for this kind of feature (?) to initiate std messages for needed
(non-cq) call.
So back to question: why double click on "band activity" should fire
TX (and disturb ongoing qso) ?
--
Saku
OH1KH
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
