Added TX split support using XIT if rig supports it. (easier than using 2 vfos)
Value 0 .. 9999Hz UP / DOWN
Keys Ctrl+1 ... Ctrl+9 quick set XIT
Key Ctrl+0 Disables XIT
Key Ctrl+9 adds random value of 0 .. 990Hz (step 10Hz) to setting if splitting is UP
Substracts if slpitting is DOWN
Split keys work when NewQSO or TRXControl window is active
Tested with Icom IC7300
Added help key Ctrl-H to "QSO list"
Works now similar as "New QSO"
Both "New QSO" and "QSO list" have also Alt-H as help key.
"QSO list" key "F1" can now be used for other purposes. The help connection still exist in source.
Fixed help files
Help for split
Shortcut keys
Made all VK_keys now called as Ctrl-, Alt- There was a mixture of plus and minus signs (Ctrl+, Ctrl-)
Squashed commit of the following:
commit bb6b50f3f6cd0ba1c6aa9bdc23f4da687d3fa7d5
Author: OH1KH <oh1kh@sral.fi>
Date: Tue Oct 27 10:30:31 2020 +0200
Small help fix and PR date to fVersion
commit 2066b993bef52cf4d1268544eae5a5538e8c6d00
Author: OH1KH <oh1kh@sral.fi>
Date: Tue Oct 27 10:19:40 2020 +0200
Added split keys to work also when trxcontrol window is active. Fixed some help files.
commit 3cd43922e5d4ac0bd7f81cb1b0308a260e321aee
Merge: 25ca1e0 b09e821
Author: OH1KH <oh1kh@sral.fi>
Date: Tue Oct 27 09:27:34 2020 +0200
Merge branch 'qso_list_help_key' into split_with_xit
commit 25ca1e07b81d0d377321ca3b38390b83aa2c2479
Author: OH1KH <oh1kh@sral.fi>
Date: Mon Oct 26 18:55:36 2020 +0200
Button position fix
commit e5ec98c443a2197f603aade6fc5d3beef4068cb3
Author: OH1KH <oh1kh@sral.fi>
Date: Mon Oct 26 18:42:22 2020 +0200
Added TX split support
Added TX split support using XIT if rig supports it. (easier than using 2 vfos)
Value 0 .. 9999Hz UP / DOWN
Keys Ctrl+1 ... Ctrl+9 quick set XIT
Key Ctrl+0 Disables XIT
Key Ctrl+9 adds random value of 0 .. 990Hz (step 10Hz) to setting if splitting is UP
Substracts if slpitting is DOWN
Fixed help files
Tested with Icom IC7300
commit b09e821a72
Author: OH1KH <oh1kh@sral.fi>
Date: Mon Oct 26 09:35:38 2020 +0200
Added help shorcut key Ctrl+H to 'QSO list'
1) fixed a bug in Club marking fied selection that I myself had done when trying to make "comment for qso" look similar in all places. At membership settings it must be named by the DB column name "remarks" (that may confuse user) so returned it to that.
2)QSO list/Statistics/Membership tracking/Rebuild membership statistices is fixed. It did set all empty marking fieds filled with club (first club's if several) mark. Now sets just ones that really are club members.
Thanks to Andreas, DL7OAP, who saved lot of my time suggesting fix. Otherwise I should have learned myself (better) for sql join to find out what is the root cause.
Squashed commit of the following:
commit e3d93ae52e
Author: OH1KH <oh1kh@sral.fi>
Date: Fri Oct 23 10:11:01 2020 +0300
Version date change
commit c8569e4051
Author: OH1KH <oh1kh@sral.fi>
Date: Thu Oct 22 17:55:34 2020 +0300
Changed left join to inner join to get proper results
commit b52c5ef945
Author: OH1KH <oh1kh@sral.fi>
Date: Wed Oct 21 18:52:44 2020 +0300
Fix for Club membership recreation
Club settings selector (where to place membership marking) had "comm. for qso"
I have messed it up a long ago when I changed terms "remarks" to "comment to qso" in several places to make similar outlook everywhere.
I did not know that this selector in club settings must have same name as cqrlog_main database field "remarks" that shows up at NewQSO with label "Comment for qso" (which is confusing)
Fixed.
This is stored in Xcqrlog.cfg so clubs must be removed, cqrlog closed and reopened and clubs added again to get it cleared.
Other way round is to export log configuration, find "comm. for qso" lines there and change them to "remarks" and import settings to log again.
That fix still leaves recreation to fail (every qso is marked as club qso). So there is another bug also.
Added limited support for speed changes in middle of macro text when using Hamlib keyer.
1) Version of Hamlib must be at least Hamlib 4.1~git Last commit 2020-10-20 03:22:59 2020 +0000 SHA=8a769c
2) Do not use space(s) between text and +(or -) rigctld will add them I.E. "TU+++599---001"
3) Speed change works only with BKIN mode (not F-BKIN) and at the moment new Icom rigs (tested only ic7300)
4) Test results for icom 7300: Macro string "TU+++5nn---001"
Speed 28WPM +15WPM increase for "5nn"
Rig settings: TX delay 25ms, BKIN delay 7.5d, CW-Key set/Rise time 2ms
Measured time for 1st dot of "5" is 0.024sec, 2nd 0.027sec.
Speed change via CAT causes 3ms drop of first element. Not fatal!
With other keyers this existed already, but forgotten from help file.
Fixed help file.
Added speed limit checks for all keyers when using + and -
Squashed commit of the following:
commit f745caa91c839e04d3f474d0b5ef59274edb6a98
Author: OH1KH <oh1kh@sral.fi>
Date: Wed Oct 21 12:07:30 2020 +0300
Added some range checking
commit a47b585813654f72bee402601b9ae306dc459985
Author: OH1KH <oh1kh@sral.fi>
Date: Tue Oct 20 17:22:43 2020 +0300
CW macro speed changes
Added limited support for speed changes in middle of macro text when using Hamlib keyer.
1) Version of Hamlib must be at least Hamlib 4.1~git Last commit 2020-10-20 03:22:59 2020 +0000 SHA=8a769c
2) Do not use space(s) between text and +(or -) rigctld will add them I.E. "TU+++599---001"
3) Speed change works only with BKIN mode (not F-BKIN) and at the moment new Icom rigs (tested only ic7300)
With other keyers this existed already, but forgotten from help file.
Fixed help file.
It seems that cmds.StrictDelimiter := true does not work as it should allowing alsi space to be delimiter with the defined delimiter character then help file is changed so that user understands to use double quotes if his command string contains spaces between.
A Lazarus bug, perhaps?
via ALT+O. This is stored in a separate table column if it differs
from the configured station callsign.
I is exported to ADIF and cbr/edi files.
Squashed commit of the following:
commit 4d9302d89ebc8d5f4f3fb0c891283310c9391e60
Author: phl0 <florian@florian-wolters.de>
Date: Thu Sep 10 02:03:51 2020 +0200
operator support for cabrillo exports
commit ffed1b5a7cd61147305ee0afd15db4e0ce80f752
Author: phl0 <florian@florian-wolters.de>
Date: Thu Sep 10 01:31:42 2020 +0200
Add operators to edi exports
commit 56ab0e5f36dfff54a8ffae05565344cb8fb717d5
Author: phl0 <florian@florian-wolters.de>
Date: Wed Sep 9 16:36:06 2020 +0200
Retain operator call on QSO edit
commit db6d23109834c8258fa87e418c004dcb253e2235
Author: phl0 <florian@florian-wolters.de>
Date: Wed Sep 9 16:26:31 2020 +0200
Add ADIF import functions for operator call
commit 9fa74745c564cf9215fd8878419b2c1042b5c1a5
Author: phl0 <florian@florian-wolters.de>
Date: Wed Sep 9 16:07:43 2020 +0200
Add export functions for operator callsign
commit c04387a4f2d0ce014aac1b1b137f2f80ecb190d7
Author: phl0 <florian@florian-wolters.de>
Date: Wed Sep 9 15:46:38 2020 +0200
Store Op only if different from configured callsign
commit b00e6ae48dcba47a9db071d7ffb5c52885672ad0
Merge: 11d851e d99e17f
Author: phl0 <florian@florian-wolters.de>
Date: Tue Sep 8 12:21:13 2020 +0200
Merge remote-tracking branch 'upstream/master' into operator
commit 11d851e7c66b9f3d91289ced4a5b0d6d857ab2e8
Merge: 7e80390 2d4445b
Author: phl0 <florian@florian-wolters.de>
Date: Mon Sep 7 12:22:26 2020 +0200
Merge remote-tracking branch 'upstream/master' into operator
commit 7e803907de50a5c3b774e31f63ce9ecf34696c4d
Author: Florian Wolters <florian@florian-wolters.de>
Date: Sun Sep 6 10:55:47 2020 +0200
Update documentation
commit 6d0dbfc2e8889b4a65b1675ea2bebdc53a7ec252
Author: phl0 <florian@florian-wolters.de>
Date: Fri Sep 4 10:47:08 2020 +0200
Slight formatting stuff
commit 620b1713ab33884a0291198d26484612bd195a95
Author: OH1KH <oh1kh@sral.fi>
Date: Thu Sep 3 17:01:10 2020 +0300
additions 2
- N1MM now gets "operator" with same rules as wsjt-x
- change loc (6) and change operator (20) now has input limit
- fChangeOperator should be now part of project (diff shows not..will check after commit)
- cabrillo export now has header "OPERATORS:"
by cabrillo definitions it can show operators and host:
OPERATORS: OH1KH,@OH1KH (when no operator defined)
OPERATORS: OH1KJ,@OH1KH
OPERATORS: OH1KH,OH1KJ,@OH1KH
The last case must be mentioned in HELP that operator (Alt+O) input can be more than one callsign by comma separated (in limit of 20 char).
commit ffd3ba2f0bceeccf2e8a4b8ad7be9c66a2209893
Author: OH1KH <oh1kh@sral.fi>
Date: Thu Sep 3 12:03:59 2020 +0300
Some additions
- fixed status line sizes: shorter text for My grid and ref.call
- added Operator to status line
- shows up if different than station call
- if changed to empty input replaces station call to be also operator
- wsjtx logging "operator" sets cqrlog operator but only if previous value was station call.
- fixed ctrl+l (myLoc) has now input validate. Allows just 6 char input now
commit 7f6db3909ecbe3c5dc397196309c0605806b0f0b
Author: phl0 <florian@florian-wolters.de>
Date: Wed Sep 2 13:31:02 2020 +0200
Add forgotten files ... :/
commit f0b1c7b94f9bf8e43005b19c5dcde18c9f5d9081
Author: phl0 <florian@florian-wolters.de>
Date: Wed Sep 2 13:30:06 2020 +0200
Add Operator short cut/ popup to save and Edit QSO functions
commit 9de6a7447293813840029e93c98ba4da844b10b5
Author: phl0 <florian@florian-wolters.de>
Date: Wed Sep 2 08:52:35 2020 +0200
Add column for operator to main DB
For some unknown reason Details window opens from Ctrl+i and Ctrl+h keys. Also from NewQSO/Window/details where only Ctrl+i is mentioned.
Help file mentions that there is a checkbox in preferences/NewQSO to make Details open at program start. How ever there is no checkbox!
By default Details opens in fresh empty log, but once closed it keeps closed on next starts.
Change:
- Details opens from NewQSO/Window/details and Ctrl+i
- Ctrl+h opens help
- shorcut keys help fixed
- NewQSO (sections: settings and operation) fixed
Fixed HTML export output to pass HTML5 validate. Also tried to make UTF-8 output true. Tested with some E77 logged calls having special characters in name or qth.
For some reason GTK2 compiled version fails to output (and show in QSO list) those characters. When compiled with QT5 display and exported HTML shows out ok.
HTML export "lang" tag is now set by operating system env variable LANG. If it fails en-EN is used as default.
Checking "Most recent qsos first" at export causes ExAscTime to be true.
Then oldest qsos are on top of export:
ExAscTime := cqrini.ReadBool('Export','AscTime',False);
if ExAscTime then
dmData.Q.SQL.Text := 'SELECT * FROM view_cqrlog_main_by_qsodate_asc'
Term "ascending order", "ASC", by qso date means rising date value that is "from oldest date to latest date".
Easiest fix is to fix the form text from "Most recent" to "Oldest". Then the text equals to source code and does what expoected.
