On 23/09/2014 18:07, Michael Black wrote:
Hi Mike,
Oh...misunderstood again....I was thinking of the side-by-side buttons
like tab 1.
Actually why shouldn't tab two have two sets of buttons for the
messages too like tab 1? Just organized differently like they are now?
I might actually use it then as I prefer to do "next msg" usually
except when I'm too late to do so and then need "Now".
Seems like there's enough visual room to do that.
I defer to Joe for route historical to the current setup. But I think
that Tab 2 is a more streamlined version of the Tx 1..6 buttons that go
back through most of the suite of programs. It seems to me that you
already have the next message feature by double clicking decodes, which
generally do the right thing. If you leave things a bit late because the
decodes are slow, or you are, then the behaviour you want is an
immediate message change anyway. It is hard to envisage a situation
where you know what message you are going to send next while you are
still transmitting the current message i.e. unless you have made a
mistake you would not click any button while transmitting unless you
have made a mistake, in which case you probably want immediate outgoing
message update.
I don't see any need to change the buttons available since tab 1 is
available for those that want deferred message sending.
As for the wording I'm just saying make Tab 1 and Tab 2 say the same
thing. So...comparing again...
Tab 1 = "Switch to this TX message NOW"
Tab 2 = "Switch to CQ message NOW" (since the message is fixed).
OK, but I still think there is ambiguity with that text (equally so with
the tab 1 "Now" label).
Underlying this is an annoyance I have with operators that click through
the message sequence without apparently reading their QSO partner
replies. It seems that some operators want every QSO to be completed in
the minimum number exchanges even if their QSO partner gives no
indication of actually confirming they have received their report!
This one just lies ahead, in annoyance, to those that send a R+ report
before I have sent them a report!
If everyone tried to use the decode double clicks to progress their QSOs
there might be less confusion on the bands.
Mike W9MDB
73
Bill
G4WJS.
*From:*Bill Somerville [mailto:[email protected]]
*Sent:* Tuesday, September 23, 2014 11:56 AM
*To:* [email protected]
*Subject:* Re: [wsjt-devel] [HamApps] Re:: Request
On 23/09/2014 17:44, Michael Black wrote:
Hi Mike,
You got two sets of buttons (regular and radio) on Tab 2???
I'm running r4333 and don't see two sets.
The buttons on tab 2 are (and have been for quite a long time):
Push button labelled "CQ" tool tip "Generate a CQ message",
push button labelled "Grid" tool tip "Generate a message for replying
to a CQ",
push button labelled "dB" tool tip "Generate message with report",
push button labelled "R+dB" tool tip "Generate message with R+ report,
push button labelled "RRR" tool tip "Generate message with RRR",
push button labelled "73" tool tip "Generate message with 73",
radio button labelled "Gen msg" tool tip "Send this (standard)
generated message",
radio button labelled "Free msg" tool tip "Send the free-text message
(max 13 characters)".
if you are not seeing that then your build id badly broken!
I'd recommend very similar wording as the Tab 1 buttons but perhaps
add the message type.
e.g. "Switch to CQ message NOW"
Maintaining some consistency that way.
So are you suggesting that instead of "Generate a CQ message" for the
"CQ" button. IMHO that is still ambiguous because the NOW only applies
in transmit mode. Your text might be taken to mean switch to transmit
immediately which is not the case.
Mike W9MDB
73
Bill
G4WJS.
*From:*Bill Somerville [mailto:[email protected]]
*Sent:* Tuesday, September 23, 2014 11:38 AM
*To:* [email protected]
<mailto:[email protected]>
*Subject:* Re: [wsjt-devel] [HamApps] Re:: Request
On 23/09/2014 17:26, Michael Black wrote:
Hi Mike,
I'm posting to the wstj list to get this off of hamapps. I've
heard some get annoyed at non-hamapps threads.
Well the request could be fulfilled by JTMacros although I doubt
Laurie would consider it of high priority.
Here is a link to the OP as you have only posted my reply to the OP
and have lost the context.
https://au.groups.yahoo.com/neo/groups/HamApps/conversations/messages/6517
Good to know about tab 2....I don't use tab 2. I was confused with
"radio buttons" since tab 2 doesn't have any...just "buttons".
Err, it does on my screen. There is a group of two radio buttons to
select standard generated or user defined free text message.
But should the hover text then say "NOW" like tab 1 says for the
buttons to maintain consistency? It's not intuitive.
All the buttons in the messages window on Tab 2 have immediate effect
in transmit mode. It may be sensible to make the tool tips explicitly
state that fact, although it is fairly obvious since the outgoing
message in the status bar is updated.
Any suggestions for wordings for each of the buttons?
Mike W9MDB
73
Bill
G4WJS.
*From:*[email protected] <mailto:[email protected]>
[mailto:[email protected]]
*Sent:* Tuesday, September 23, 2014 11:18 AM
*To:* [email protected] <mailto:[email protected]>
*Subject:* Re:: RE: [HamApps] Re:: Request
Hi Mike,
that is correct for the "Tab 1" messages but not the "Tab 2" messages
which are the ones I suspect most operators use.
Laurie could choose to "click" the radio button if "Tab 1" were active
and JTMacros writes the free text field "Tx 5". Alternatively WSJT-X
could do that on any modification to the free text edit.
73
Bill
G4WJS.
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
