On 17/03/2015 04:10, Michael Black wrote:
Hi Mike,
I'd like to suggest that the Tx 6 auto select after 73 not be done if
Enable is not on.
It's a bit disconcerting to click Tx 5 after the minute has started
and see the TX 6 get selected immediately. Makes sense if Enable is
on given the new behavior…but not if it's turned off.
Just to clarify, under what circumstances would selecting message 6 not
be correct?
Your last statement isn't quite logical, the selection of message 6
doesn't happen until you click enable, so enable is turned on when it
happens. I can see that it might be a little disconcerting as it all
happens in an instant. Would adding a short delay before message 6 is
selected work better.
Matter of fact…I'm thinking perhaps a checkbox next to Tx 6 that is
"Enable CQ select after 73 – must click Enable too" or such. So that
action is only performed if you want it.
I don't think that will help as it is going to confuse more users that
it helps IMHO.
I know it doesn't make a practical difference but aesthetically having
an action performed that is illogical/unnecessary is what got me.
I don't see what is illogical or unnecessary here, the application is
only doing what we discussed. Am I missing some use case where you want
to send your 73 message more than once? I would have thought that is
rare enough to justify having to click two widgets ("73" or "Tx6" then
"Enable Tx") to make it happen.
Mike W9MDB
73
Bill
G4WJS.
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
