b9b3d1d6f5
A slightly better solution to fix the 55 Hz problem with OmniRig v1.19 and later.
2022-05-03 15:46:17 +02:00
eef441ec87
Add some documentation.
2022-05-03 13:45:02 +02:00
855daf92c4
Fix 55 Hz problem with Omnirig v1.19 and later (until we have a better solution).
2022-05-02 22:06:45 +02:00
aa1225ff96
Remove local event loops from Omni-Rig interface
...
Using a local event loop to wait for Omni-Rig to initialize has caused
issues elsewhere, reverted to simple waits in teh hope that Omni-Rig
initializes promptly.
2021-07-30 20:21:57 +01:00
f972fc18e1
Remove direct struct access from usage of the Hamlib API
...
Preparation for safe dynamic linking to Hamlib where minor Hamlib
upgrades can be deployed just by replacing the DLL/SO.
2021-02-02 22:45:45 +00:00
fe4c2b59ee
Revert to narrow character logging
2020-09-27 16:52:19 +01:00
396f128ece
Make use of different severities for rig control logging
2020-09-26 15:13:29 +01:00
1d43ddd38b
Use wide character logging for efficiency as most o/p is QString
2020-09-26 14:56:16 +01:00
cbd4f109a8
Add a log channel for rig control
...
RIGCTRL is defined as a log channel for rig control messages and the
appropriate logger is made available to children of the Transceiver
class. Use Transceiver::logger() to access the logger.
Switched existing rig control QDebug messages to Boost logging.
2020-09-25 02:37:41 +01:00
0c3fa17865
Avoid an uninitialized COM pointer reference in the Omni-Rig i/f
...
Removed port locking as it doesn't seem to work.
2020-05-29 23:38:55 +01:00
ad4e196d13
Handle attempts to use Omni-Rig when not installed more gracefully
2020-04-12 22:09:06 +01:00
fb1b2e7687
Merge tag 'wsjtx-2.1.1' into develop
...
Tagging the WSJT-X v2.1.1 release
2019-11-24 21:24:39 +00:00
ee5d5c8ae9
improve physical structure
2019-07-02 10:19:43 -05:00
Uwe Risse
Bill Somerville
sirhc808