User Guide updates for a 2.3.1 hot fix release

Mostly bringing images up to date with the 2.3.0
implementation. Includes removal of all sign of Tab 2 messages.
This commit is contained in:
Bill Somerville 2021-02-10 20:27:10 +00:00
parent 7c76d83ef0
commit 66328af02a
No known key found for this signature in database
GPG Key ID: D864B06D1E81618F
24 changed files with 44 additions and 38 deletions

View File

@ -37,6 +37,12 @@ examples for configurations `FT8` and `Echo`:
==== View Menu
image::view-menu.png[align="left",alt="View Menu"]
The *SWL Mode* action reduces the _WSJT-X_ main window to a minimum
size with just the menus, decodes windows, and status bar visible. You
may find this useful when running multiple instances of the
application. Both size and location of the main window are saved and
recalled independently for this view.
[[MODE_MENU]]
==== Mode Menu
image::mode-menu.png[align="left",alt="Mode Menu"]

View File

@ -1,11 +1,10 @@
// Status=edited
Two arrangements of controls are provided for generating and selecting
Tx messages. Controls familiar to users of program _WSJT_
appear on *Tab 1*, providing six fields for message entry.
Pre-formatted messages for the standard minimal QSO are generated when
you click *Generate Std Msgs* or double-click on an appropriate line
in one of the decoded text windows.
Controls familiar to users of program _WSJT_ appear on *Tab 1*,
providing six fields for message entry. Pre-formatted messages for
the standard minimal QSO are generated when you click *Generate Std
Msgs* or double-click on an appropriate line in one of the decoded
text windows.
//.Traditional Message Menu
image::traditional-msg-box.png[align="center",alt="Traditional Message Menu"]
@ -28,31 +27,12 @@ stored messages entered on the *Files -> Settings -> Tx Macros* tab.
Pressing *Enter* on a modified message #5 automatically adds that
message to the stored macros.
* In some circumstances it may be desirable to make your QSOs as
short as possible. To configure the program to start contacts with
message #2, disable message #1 by double-clicking its radio-button in the *Next* column or *Tx 1* button in the *Now* column. Similarly, to send RR73
rather than RRR for message #4, double-click one of its buttons.
The second arrangement of controls for generating and selecting
Tx messages appears on *Tab 2* of the Message Control Panel:
//.New Message Menu
image::new-msg-box.png[align="center",alt="New Message Menu"]
With this setup you normally follow a top-to-bottom sequence of
transmissions from the left column if you are calling CQ, or the right
column if answering a CQ.
* Clicking a button puts the appropriate message in the *Gen Msg* box.
If you are already transmitting, the Tx message is changed
immediately.
* You can enter and transmit anything (up to 13 characters, including
spaces) in the *Free Msg* box.
* Click the pull-down arrow in the *Free Msg* box to select a
stored macro. Pressing *Enter* on a modified message here
automatically adds that message to the table of stored macros.
* In some circumstances it may be desirable to make your QSOs as short
as possible. To configure the program to start contacts with message
#2, disable message #1 by double-clicking its radio-button in the
*Next* column or *Tx 1* button in the *Now* column. Similarly, to
send RR73 rather than RRR for message #4, double-click one of its
buttons.
+

Binary file not shown.

Before

Width:  |  Height:  |  Size: 230 KiB

After

Width:  |  Height:  |  Size: 134 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 7.4 KiB

After

Width:  |  Height:  |  Size: 5.9 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 161 KiB

After

Width:  |  Height:  |  Size: 175 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 22 KiB

After

Width:  |  Height:  |  Size: 24 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 52 KiB

After

Width:  |  Height:  |  Size: 38 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 30 KiB

After

Width:  |  Height:  |  Size: 29 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 2.9 KiB

After

Width:  |  Height:  |  Size: 3.5 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 7.2 KiB

After

Width:  |  Height:  |  Size: 8.7 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 33 KiB

After

Width:  |  Height:  |  Size: 47 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 9.4 KiB

After

Width:  |  Height:  |  Size: 16 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 82 KiB

After

Width:  |  Height:  |  Size: 98 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 4.5 KiB

After

Width:  |  Height:  |  Size: 5.0 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 22 KiB

After

Width:  |  Height:  |  Size: 23 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 22 KiB

After

Width:  |  Height:  |  Size: 26 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 4.3 KiB

After

Width:  |  Height:  |  Size: 5.5 KiB

View File

@ -160,7 +160,7 @@ guidelines for contest logging with FT4, FT8, and MSK144:
[[COMP-CALL]]
=== Nonstandard Callsigns
*FT4, FT8, and MSK144*
*FT4, FT8, FST4, and MSK144*
Compound callsigns like xx/K1ABC or K1ABC/x and special event
callsigns like YW18FIFA are supported for normal QSOs but not for

View File

@ -18,6 +18,13 @@ image::colors.png[align="center",alt="Colors Screen"]
* Check *Highlight by Mode* if you wish worked before status to be per
<<INTRO,mode>>.
* Check *Only grid Fields sought* if you are only interested in the
leading two character grid locator Fields rather than teh four
character grid locator Squares.
* Check *Include extra WAE entities* if you are interested in the
extra entities defined for DARC WAE and CQ Marathon awards.
* Worked before status is calculated from your _WSJT-X_ ADIF
<<LOGGING, Logging>> file, you may replace ADIF log file with one
exported from your station logging application, *Rescan ADIF Log*

View File

@ -96,5 +96,6 @@ green to indicate that proper communication has been established.
Failure of the CAT-control test turns the button red and displays an
error message. After a successful CAT test, toggle the *Test PTT*
button to confirm that your selected method of T/R control is working
properly. (If you selected *VOX* for _PTT Method_, you can test T/R
properly, the button turns red if the rig has been successfully
keyed. (If you selected *VOX* for _PTT Method_, you can test T/R
switching later by using the *Tune* button on the main window.)

View File

@ -19,6 +19,10 @@ QRZ messages. Full details of the protocol can be found in comments
at the top of this file in our source code repository:
https://sourceforge.net/p/wsjt/wsjtx/ci/master/tree/Network/NetworkMessage.hpp
NOTE: The *Outgoing interfaces* and *Multicast TTL* fields are only
present when a multicast group IP address has been entered in
the *UDP Server* field.
Programs like _JTAlert_ use the _UDP Server_ feature to obtain
information about running _WSJT-X_ instances. If you are using
_JTAlert_ to control _WSJT-X_, be sure to check the

View File

@ -16,6 +16,5 @@ characters) in the entry field at top, then click *Add*.
- You can reorder your macro messages by using drag-and-drop. The
new order will be preserved when _WSJT-X_ is restarted.
- Messages can also be added from the main window's *Tx5* field on Tab
1 or the *Free msg* field on Tab 2. Simply hit [Enter] after the
message has been entered.
- Messages can also be added from the main window's *Tx5*
field. Simply hit [Enter] after the message has been entered.

View File

@ -381,7 +381,7 @@ decode*, *Decode after EME delay*
.Wide Graph:
- *Bins/Pixel* = 3, *N Avg* = 10
- *Bins/Pixel* = 4, *N Avg* = 10
- Adjust the width of the window so that the frequency range extends
up to at least 2400 Hz.

View File

@ -119,6 +119,15 @@ In macOS, enter the following command from a terminal:
open /Applications/wsjtx.app --args -stylesheet :/qdarkstyle/style.qss
In Linux using the Unity or GNOME GUI the following commands will
update the _WSJT-X_ start up:
....
sed '/Exec=wsjtx/ s/$/ -stylesheet :\/qdarkstyle\/style.qss/' \
/usr/share/applications/wsjtx.desktop >~/.local/share/applications/wsjtx.desktop
update-desktop-database ~/.local/share/applications/
....
Depending on your operating system, the main _WSJT-X_ window will look
something like this: