I don't see anything in there about serialization...but here's a thread which
shows some examples and says "don't do it" referring to pass by reference.
https://stackoverflow.com/questions/8455887/stack-object-qt-signal-and-parameter-as-reference
Mike
On Thursday, January 24, 2019, 5:22:36
Hi Steve,
wouldn't it be a good idea to include those hints as "known issues" in
the the release notes for the current version, because several users
have reported those false decodesrecently. I've had a couple of those,
too. I remember that in several sections of the user guide it is
recomm
On 24/01/2019 23:07, Black Michael via wsjt-devel wrote:
And where does this serialization take place? Are you saying it's a
default condition of Qt to serialize across event boundaries?
de Mike W9MDB
Mike,
you need to read up on the Qt signal/slot mechanism and how queued
signals are proc
And where does this serialization take place? Are you saying it's a default
condition of Qt to serialize across event boundaries?
de Mike W9MDB
On Thursday, January 24, 2019, 4:05:37 PM CST, Bill Somerville
wrote:
On 24/01/2019 21:07, Black Michael via wsjt-devel wrote:
If app
On 24/01/2019 22:45, Black Michael via wsjt-devel wrote:
Here's more context
Hi Mike,
I need more than that. It looks like PTT has just been set, is this a
"Test PTT" button click? What Hamlib backend is being used and how is
CAT and PTT configured?
73
Bill
G4WJS.
__
Could be a buffer flushing problem on the segfault.
Here's more context
[20190124 06:32:14.097 Eastern Standard Time D]
C:\JTSDK-Tools\tmp\wsjtx\HamlibTransceiver.cpp:1017 -
"HamlibTransceiver::poll:" rig_get_ptt PTT = 0[20190124 06:32:15.061 Eastern
Standard Time D] C:\JTSDK-
On 24/01/2019 21:07, Black Michael via wsjt-devel wrote:
If appears to me that the new_state variable is passed by reference to
the update event and it may be losing scope before being handled.
Hi Mike,
I doubt that. The signal is not crossing a thread boundary so it will
simply be a functio
I'm working with a user who was running a Flex and split=Fake It.
The last line of his debug log showed this:[20190124 06:32:15.061 Eastern
Standard Time D] C:\JTSDK-Tools\tmp\wsjtx\EmulateSplitTransceiver.cpp:41 -
EmulateSplitTransceiver::handle_update: from wrapped:
Transc
Guys,
Fedora Rawhide has updated to gcc 9.0.0 and as usual the compiler gets more
pedantic about code and has raised some new errors with the fortran code of
wsjtx. Since it stops at the first error and I've already seen two with
different compile attempts it may take a few iterations to fix them
VK2/G3NJV.
Paul,
In addition to being active using WSJT-X v2.0.0 784f75 , I also run a
Redpitaya to decode FT8 stations and feed the FT8 RBN as well as PSK
reporter. My spot of you may also have been from the RP receiver/decoder.
73,
Rich - K1HTV
= = =
From: Paul Randall
To: "wsjt-devel@lists.s
On 1/24/19 6:44 AM, Bill Somerville wrote:
> I am fairly confident that given a mode that might have the sensitivity
> of WSPR-15, on LF bands, with similar or less bandwidth and similar T/R
> period to WSPR-2, users would consider upgrading their transmitters for
> the necessary frequency stabi
Hi Paul,
Recently, we’ve introduced a couple of techniques that have significantly
improved the sensitivity of WSPR-2. Increased sensitivity comes with higher
probability of false decodes. The next release of WSJT-X will fix a bug that
should eliminate some of those false decodes - but it will
Hi Phil
It says in the WSJT v2 user guide section 7.5 “WSJT-X 2.0 offers no support for
two nonstandard callsigns to work each other” so this is a well known
limitation.
I do not understand the logic that WSJT does not give reception reports to PSK
reporter unless a QRA and callsign exist in a
Hi Bill,
Thanks for your reply. Well, reducing also the spaces when hiding the menu bar
is a good idea. However, as unfortunately the height of the control panel is
NOT reduced (only the minimum width), for 16/9 monitors in practice it doesn’t
bring any advantage. Just as an idea for future
On 24/01/2019 11:00, N1BUG wrote:
On 1/24/19 5:41 AM, Bill Somerville wrote:
On the new lower LF bands a decoder can take advantage of the far more
stable propagation than is found on the higher short-wave bands.
Coherence across significant periods of time allows assumptions that
frequency and
On 1/24/19 5:41 AM, Bill Somerville wrote:
> On the new lower LF bands a decoder can take advantage of the far more
> stable propagation than is found on the higher short-wave bands.
> Coherence across significant periods of time allows assumptions that
> frequency and phase of a signal are esse
On 24/01/2019 10:29, N1BUG wrote:
I want to inquire one more time about WSPR-15. Is this mode finally
declared forever abandoned or is there still some hope it will find
its way into WSJT-X?
Hi Paul,
there has been some work on a WSPR-LF mode that should perform at least
as well as WSPR-15, o
I want to inquire one more time about WSPR-15. Is this mode finally
declared forever abandoned or is there still some hope it will find
its way into WSJT-X?
I must emphasize WSPR-15 is the miracle beacon and propagation study
mode for LF, where it is still used every day. As one example:
recently
On 24/01/2019 07:23, OG55W wrote:
One minor issue: The layout for the various fields in WSJT-X v2.0.0 is
somewhat different when “Menus” is enabled or disabled. (My preferred
layout is that when menus are enabled, but usually I like the menus
disabled…). Not a big deal, but maybe it can be co
On 24/01/2019 08:26, t...@gmx.fr wrote:
Hi,
Paul, I have the same issue when I use the call ZS1/F5FDV.
Since december last year I was wondering why I get only few reports
from PSKReporter.
Your post provides a very relevant the explanation, in my opinion.
Reporting went well with revisions prio
I want to report two new behaviors with WSPR in 2.0.0 that were not
occurring with prior versions.
1. Occasionally a known / real call sign will decode with an
incorrect grid. Usually the grid is thousands of miles from where it
should be, sometimes in the arctic or the middle of an ocean. A look
Hi,
Paul, I have the same issue when I use the call ZS1/F5FDV.
Since december last year I was wondering why I get only few reports from PSKReporter.
Your post provides a very relevant the explanation, in my opinion.
Reporting went well with revisions prior to 2.0.
It seems consist
22 matches
Mail list logo
