Joe,
2. Checkbox "Lock Tx Freq" on main window is relabled "Hold Tx Freq".
I like this change it accurately reflects what I see the program doing.
3. Behavior now defaults to the "simplex" behavior in use up to code
revision r8123. In particular, double-clicking on decoded mesages
that do not contain your own call moves both Rx and Tx frequencies.
If the first callsign is your own call, only Rx freq moves.
All of the items in Point 3 appear to be working in a limited test this
afternoon. I think this is the best operation yet, as far as working split
vs. simplex goes.
4. If "Hold Tx Freq" is checked, double-clicking on decoded messages
moves the Rx frequency; Tx frequency is moved only if CTRL was held
down.
This appears to work as described. I like the functionality.
5. Clicking on the waterfall moves Rx and Tx frequencies as before:
Rx only on a simple click, Tx only on SHIFT-click, and both on
CTRL-click. This happens even if "Hold Tx Freq" is checked (which
is why this box is no longer labeled "Lock Tx Freq").
This is perfect as well.
I think you've hit on a setup that will fit most use cases and not leave
anyone stranded with a broken workflow. Thank you for your hard work!
73,
KC9SWV - Morgen
President, TARA
On Sat, Sep 30, 2017 at 2:00 PM, Joe Taylor <j...@princeton.edu> wrote:
> Hi all,
>
> Changes in program behavior can be confusing, so I apologize for some
> recent instability in GUI operational behavior. Code revision r8146 is yet
> another attempt to get it right -- or as near "right" as possible -- while
> supporting both simplex and split-frequency default operating styles.
>
> The following is the commit message for r8146:
>
> ##########################################################################
> Another try at optimizing the GUI for simplex and split behavior. Details
> below:
>
> 1. Checkbox "Double-click on call sets Tx and Rx freqs" has been removed
> from the Settings -> General tab.
>
> 2. Checkbox "Lock Tx Freq" on main window is relabled "Hold Tx Freq".
>
> 3. Behavior now defaults to the "simplex" behavior in use up to code
> revision r8123. In particular, double-clicking on decoded mesages
> that do not contain your own call moves both Rx and Tx frequencies.
> If the first callsign is your own call, only Rx freq moves.
>
> 4. If "Hold Tx Freq" is checked, double-clicking on decoded messages
> moves the Rx frequency; Tx frequency is moved only if CTRL was held
> down.
>
> 5. Clicking on the waterfall moves Rx and Tx frequencies as before:
> Rx only on a simple click, Tx only on SHIFT-click, and both on
> CTRL-click. This happens even if "Hold Tx Freq" is checked (which
> is why this box is no longer labeled "Lock Tx Freq").
> ##########################################################################
>
> If I have not made mistakes, this arrangement should provide full backward
> compatibility and also easy assertion of a mode that keeps your Tx
> frequency fixed until you explicitly change it.
>
> If you can build r8146 for yourself and try it on the air, please post
> your comments here.
>
> -- 73, Joe, K1JT
>
> ------------------------------------------------------------
> ------------------
> 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
>
------------------------------------------------------------------------------
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
