It's a bit more complicated than that. You have to specify a QColor format
first. and the colour components are doubled up.
This gives me red background with white foreground :-
byte[] byteBackgroundQColor = new[] { 1, 255, 255, 255, 255, 0, 0, 0, 0, 0,
0 }; // format =1 then Red AA RR GG BB
Hi All,
I have modified WSJTX 2.0.0 (old version rather than 2.0.1 because I
don't want to switch versions mid project) to produce 12000 samples per
second wav files for data analysis.
The files produced work properly for every mode, both fast and slow,
except for JT4. I did not mess with a
Looks like four 16-bit integers r,g,b,alpha
de Mike W9MDB
On Wednesday, April 3, 2019, 10:45:49 PM CDT, Ed Stokes
wrote:
With reference to NETWORK_MESSAGE_HPP
Highlight Callsign In 13 quint32 *
Id (unique key) utf8 *
With reference to NETWORK_MESSAGE_HPP
Highlight Callsign In 13 quint32
* Id (unique key)utf8
* Callsign utf8
* Background Color QColor
* Foreground
.-. .-.
... as a massive stroke survivor (7/25/14).
Keep pounding away!
73 de W8NET Miles / “Gene”
Secretary, Portage County Amateur Radio Service (PCARS)
3905 Century Club - Master #47
Licensed since 1974
> On Apr 3, 2019, at 6:10 PM, Topher Petty wrote:
>
> Jari:
>
> Just keep doing what
> On Apr 3, 2019, at 13:28, Gary Hinson wrote:
>
> [In just a few years when propagation is better and the FT8 frequencies
> become crowded, auto-responding to the weakest callers first will make even
> more sense.]
I’ve wanted this feature for a long time. Not necessarily the lowest/weake
Jari:
Just keep doing what you're doing. As a fellow handicapped HAM, I say do
what you enjoy.
I've been known to send off the occasional email to other operators who are
experiencing issues with their rigs, and I do so in as helpful of a tone as
I can... Some really try to fix it, and others cou
Can you run rigctld with WSJT-X using "Hamlib NET rigctl" and send the output?
>From a cmd prompt...you may get a firewall warning you need to
>acceptrigctld-wsjtx -m 122 -r COM1 -s 9600 -v >log.txt 2>&1
WSJT-X should be able to hook up to it...duplicate your problem...then send
log.txt t
Known issue ... crept in v2.0.1. Will be fixed in next release.
Workaround is to keep on what you've been doing for now.
Neil, KN3ILZ
On 4/2/2019 7:35 PM, Geoffrey Mendenhall wrote:
The LoTW color highlighting no longer works when WSJT-x loads even
though the current file: " lotw-user-act
Hi All,
I try to debug a strange program operation on first start up after OS boot.
windows 10 ver 1809
hamlib as git clone git://git.code.sf.net/u/bsomervi/hamlib
u-bsomervi-hamlib (integration branch)
Radio is FT857 via hamlib
wsjt-x 2.0.1
The question is why the radio go to 7075 Khz, not t
Hi Tom.
Yes, a robot FT8 CQer that instantly jumped to the frequencies of its chosen
callers would be a nightmare, especially if it then stayed put to call CQ.
There are still quite a few [human|robot] stations who either don’t understand
or simply disagree with split-by-default on FT8 …
The LoTW color highlighting no longer works when WSJT-x loads even though the
current file: " lotw-user-activity.csv " is in the WSJT-x LOG directory.
This feature worked OK in WSJT-x v 2.0.0
The only way to get the LoTW highlighting to work now is to go to
SETTINGS/COLORS and execute the FET
Hello Jari, I’m happy to see that we’ve made contact on my little
JW-expedition. These days it seems that SSB is closed from here, but a few FT8
signals are maiking it. As far as robots are concerned, I cannot do coding, but
I wonder if the urge to have the «hold tx freq» unticked is robotic or
Den 27.03.2019 12:39, skrev Magne Mæhre:
A couple of my club mates have written about a weird issues which showed
up when trying to use WSJT-X with an IC-9100. I've seen the same
issues with IC-7100 as well. Even though WSJT-X is not the real culprit
here, I thought some of you might find it
14 matches
Mail list logo
