No good.
Now it is selecable via CW Messages setting form what will happen if ENTER is pressed while Memory keys/some button is still focused.
- repeat focused button sending
- ingnore enter
- save qso
Squashed commit of the following:
commit 50bb63a689be0b06f340f1ddfff676c9899fc69d
Author: OH1KH <oh1kh@sral.fi>
Date: Mon Feb 24 12:20:40 2020 +0200
Small fix to help
commit b6e2c7ab64
Author: OH1KH <oh1kh@sral.fi>
Date: Mon Feb 24 12:02:27 2020 +0200
Renamed form Key macros to CW Memories, and help fix
commit a919578de1
Author: OH1KH <oh1kh@sral.fi>
Date: Mon Feb 24 11:49:02 2020 +0200
Renamed form Key macros to CW memories (as in NewQSO/File/CW macros launch menu)
commit 9c27ad89de
Author: OH1KH <oh1kh@sral.fi>
Date: Mon Feb 24 11:19:55 2020 +0200
Added 3rd selection 'ignore'
commit 2f17d58e5d
Author: OH1KH <oh1kh@sral.fi>
Date: Sat Feb 22 16:40:44 2020 +0200
help files update
commit 3bb35a766a
Author: OH1KH <oh1kh@sral.fi>
Date: Sat Feb 22 12:35:14 2020 +0200
Selectable ENTER function by CW memory setting: repeat last clicked mem or save qso
commit 894d6152f7
Author: OH1KH <oh1kh@sral.fi>
Date: Sat Feb 22 11:39:29 2020 +0200
Enter saves qso when form memoryKeys is active
When Ctr-W is pressed creates DX spot to be sent to DXCuster from NewQSO window,
or if it is empty from last logged qso (This is as it was before).
If button "+ModeRst is pressed adds mode and RST_sent to spot text (from NewQSO, or last logged qso)
If button "+Locators" is pressed adds both locators (mine & his from NewQSO, or last logged qso)
separated by "<>". If propagation is set from NewQSO/Satellit/Propagation it is added between separators.
Both additions can occur only once in spot text ( pos(addition,spot)=0 ).
Deleting or modifying additions must be done by using keyboard after they are inserted to spot text.
Squashed commit of the following:
commit 0ebdc934c5
Author: OH1KH <oh1kh@sral.fi>
Date: Thu Jan 30 16:44:12 2020 +0200
Help update
commit 2e33a63962
Author: OH1KH <oh1kh@sral.fi>
Date: Wed Jan 29 19:16:07 2020 +0200
Added propagation mode between <> (locators)
commit 3dd4b9c2a3
Author: OH1KH <oh1kh@sral.fi>
Date: Tue Jan 28 09:18:48 2020 +0200
fixed line breaks
commit 6e04db79cf
Author: OH1KH <oh1kh@sral.fi>
Date: Tue Jan 28 09:15:12 2020 +0200
buttons for add Mode_rst and locators to spot. + Help files update
commit 67ec262e06
Author: OH1KH <oh1kh@sral.fi>
Date: Tue Jan 28 06:57:23 2020 +0200
backup cmt
Common to all keyers:
F1 .. F10 CW-keys (from keyboard) works now if NewQSO, CWKeys or CWType window is active
F1 .. F10 keyboard auto repeat disabled (long keypress do not fill CW buffers)
CW is now sent only if rig mode (NewQSO/mode selector) is CW
Windows/CWType is not visible in menu list if keyer is set to "None" at Preferences/CW interface
Moving rig from other mode to CW sends "stop keying" (specially Hamlib/rig buffer may contain old morse in some cases)
Source code is cleaned up (removed duplicate blocks, etc.)
HamLib keyer:
Tried to make Hamlib keyer handshake better. Now messages up tp 10 characters are sent by one hamlib command,
longer messages are sent letter by letter.
Tested with WinKeyer and Hamlib keyer (Icom IC7300) modes. (I have no other keyers)
Squashed commit of the following:
commit 01c977f6fa
Author: OH1KH <oh1kh@sral.fi>
Date: Mon Jan 27 16:18:32 2020 +0200
Fixed CWkeyer=None bug. Renamed CWkeys and fldig xmlrpc windows. CWType not visible in window-menu if CWkeyer=none
commit 11af0b6785
Author: OH1KH <oh1kh@sral.fi>
Date: Sat Jan 25 11:17:09 2020 +0200
CWType layout fix
commit deeb091a36
Author: OH1KH <oh1kh@sral.fi>
Date: Sat Jan 25 06:30:53 2020 +0200
Cleaned up CWinit code
commit 8054a77710
Author: OH1KH <oh1kh@sral.fi>
Date: Sat Jan 25 06:00:08 2020 +0200
Some form CWType fixes. Tested now with WinKeyer and HamLib
commit 01feb59b88
Author: OH1KH <oh1kh@sral.fi>
Date: Fri Jan 24 17:36:14 2020 +0200
Be sure mode is CW before sending to keyer
commit e41fa781d8
Author: OH1KH <oh1kh@sral.fi>
Date: Wed Jan 22 19:26:27 2020 +0200
Flush (stop)CW when entering to CW mode
commit b93b35b200
Author: OH1KH <oh1kh@sral.fi>
Date: Wed Jan 22 12:55:58 2020 +0200
Fkeys-CW only when CW mode. Hamlib handsahake fix
commit 06ff5beeb3
Author: OH1KH <oh1kh@sral.fi>
Date: Mon Jan 20 12:38:04 2020 +0200
button click does not lock Fkey
commit 888334ed2e
Author: OH1KH <oh1kh@sral.fi>
Date: Mon Jan 20 12:23:48 2020 +0200
Removed a debug print
commit fafd570a0b
Author: OH1KH <oh1kh@sral.fi>
Date: Mon Jan 20 12:19:00 2020 +0200
String lenght over 10 is sent now letter by letter. Trimmed some parts of code
commit a88bd36289
Author: OH1KH <oh1kh@sral.fi>
Date: Sun Jan 19 15:37:25 2020 +0200
Still buffering problem exist
commit 093fadf698
Author: OH1KH <oh1kh@sral.fi>
Date: Sun Jan 19 15:12:20 2020 +0200
Cleaned some debug code
commit 29c26e3847
Author: OH1KH <oh1kh@sral.fi>
Date: Sun Jan 19 15:00:28 2020 +0200
Prevent F-key repeats(need key up).Cleaned some CW code. F-keys work now also if 'CW keys' form is active. Improved HamLib Morse sending response readings (HamLib itself still has problem with buffering)
commit 8f5cf3e268
Author: OH1KH <oh1kh@sral.fi>
Date: Sun Jan 19 12:00:35 2020 +0200
Backup push. Nothing ready yet
