On 10/06/2015 13:19, Steven Franke wrote:
Bill,
Hi Steve,
I noticed that callsigns retrieved from the hashtable are not being displayed
in the spots window. The callsign is visible in ALL_WSPR.TXT, with the
customary callsign notation, however the callsign field is blank in the
spots
Bill,
I noticed that callsigns retrieved from the hashtable are not being displayed
in the spots window. The callsign is visible in ALL_WSPR.TXT, with the
customary callsign notation, however the callsign field is blank in the spots
window.
Steve k9an
Hi again,
further update - looks like the C function nhash_() is receiving args by
value but is called from Fortran which passes by reference.
I will see if I can sort it out.
73
Bill
G4WJS.
On 10/06/2015 14:49, Bill Somerville wrote:
Hi Steve probably Joe,
I have a change to deal with
Hi Steve probably Joe,
I have a change to deal with this, I think. But when I tried to test it
out by sending a WSPR Tx from a local instance of WSJT-X using the call
PJ4/K1ABC and grid FK52ud the first Tx goes Ok but WSJT-X crashes with
the following stack trace just as it is about to
Yes, that’s it.
I think that this is my fault, though I’m not sure how it came about.
If you look at nhash.c back in wsprx:
uint32_t nhash_( const void *key, int *length0, uint32_t *initval0)
compared to the current nhash.c in wsjtx:
uint32_t nhash_( const void *key, size_t length, uint32_t
Hi Bill,
On 6/10/2015 10:03 AM, Bill Somerville wrote:
Hi again,
further update - looks like the C function nhash_() is receiving args by
value but is called from Fortran which passes by reference.
You're exactly right. Compare the nhash.c that's now in the wsjtx
branch with the one in the
On 10/06/2015 15:18, Joe Taylor wrote:
Hi Bill,
Hi Joe Steve,
On 6/10/2015 10:03 AM, Bill Somerville wrote:
Hi again,
further update - looks like the C function nhash_() is receiving args by
value but is called from Fortran which passes by reference.
You're exactly right. Compare the
On 10/06/2015 13:19, Steven Franke wrote:
Bill,
Hi Steve,
I noticed that callsigns retrieved from the hashtable are not being displayed
in the spots window. The callsign is visible in ALL_WSPR.TXT, with the
customary callsign notation, however the callsign field is blank in the
spots
Hi Bill,
Since you're working on code in the WSJT trunk, presumably to be saved
there in due course, I am copying this message to the wsjt-devel
reflector. In future, let's carry on our discussion there, so others in
the development group can know what's happening.
I'm OK with including
Hi Bill,
After your recent C/Fortran fixes to nhash.c, I can no longer compile because
size_t is not defined. This change got it to compile:
Index: lib/wsprd/nhash.h
===
--- lib/wsprd/nhash.h (revision 5576)
+++ lib/wsprd/nhash.h
On 10/06/2015 20:57, Steven Franke wrote:
Hi Bill,
Hi Steve,
After your recent C/Fortran fixes to nhash.c, I can no longer compile because
size_t is not defined. This change got it to compile:
Index: lib/wsprd/nhash.h
===
---
Hi Bill, Edson, and all,
Font selections are only hints. The final choice is made by the system.
Setting fonts directly on widgets will not work because of the way style
sheets override widget fonts.
Sure, I understand these things. My intended question was how best to
address the issue in
Hi Bill,
Feel free to fix it the right way, hi. :-)
-- Joe
On 6/10/2015 4:36 PM, Bill Somerville wrote:
On 10/06/2015 21:24, Joe Taylor wrote:
Hi Joe,
Sorry guys, I fixed this a couple of hours ago and thought I had
committed it. Guess I forgot. It's fixed now, in r5577.
Hi hi,
Hi Charlie and all,
On 6/10/2015 12:50 PM, char...@sucklingfamily.free-online.co.uk wrote:
Hi Joe
Works fine, thanks! Checked over a 20dB range and seems very accurate.
For a given slider position, I believe the level is higher now than it was
previously.
Should be no change with the
On 10/06/2015 21:10, Steven Franke wrote:
...
Sorry about that, the stdint.h situation has always been a mess. Qt and
C++ both have headers that resolve this without needing to use
preprocessor conditionals in user code but I left the code as vanilla C
and I forget the quirks of C.
Thanks for
On 10/06/2015 21:24, Joe Taylor wrote:
Hi Joe,
Sorry guys, I fixed this a couple of hours ago and thought I had
committed it. Guess I forgot. It's fixed now, in r5577.
Hi hi, both racing to fix a defect I put in, apologies again.
One small comment, it is considered good practice to have the
Joe,
Fonts across different platforms is a major source of headaches in making
software portable. Even fonts of the same family can vary across operating
systems. But it is possible.
The problem you are seeing is likely to be due to Qt not finding the chosen
font, trying to search for something
On Jun 10, 2015, at 3:02 PM, Bill Somerville g4...@classdesign.com wrote:
On 10/06/2015 20:57, Steven Franke wrote:
Hi Bill,
Hi Steve,
After your recent C/Fortran fixes to nhash.c, I can no longer compile
because size_t is not defined. This change got it to compile:
Index:
On 10/06/2015 17:14, Joe Taylor wrote:
Hi Bill and all,
Hi Joe,
FYI: While echo-testing with his 10 GHz EME setup, Charlie (G3WDG)
discovered that reducing power by 3 dB using our Pwr slider actually
reduced his power by 6 dB.
We are, of course, adjusting voltage rather than power, so line
Can anyone help me to understand how to make the on-screen appearance of
WSJT-X look more uniform, across platforms and OS settings?
To see one example that bugs me, look at the Astronomical Data windows
in screen shots of Echo mode at my station and G3WDG:
Hi Joe
Re slider
I understand now why the levels anywhere other than 0dB are higher than
before.
I personally like 30dB range as it allows at least 20dB of linear adjustment
with margin for saturation at the top end. I will need to adjust the
attenuation between PC and mic input though. The
On 10/06/2015 18:09, Joe Taylor wrote:
Hi Charlie and all,
Hi Joe,
On 6/10/2015 12:50 PM, char...@sucklingfamily.free-online.co.uk wrote:
Hi Joe
Works fine, thanks! Checked over a 20dB range and seems very accurate.
For a given slider position, I believe the level is higher now than it was
Bill,
r5578 builds on my Mac.
Scott D. Hernalsteen/W8CQD
FCC Licensed Amateur Radio Operator
(Amateur Extra Class)
www.w8cqd.com
To preserve liberty it is essential that the whole body of the people always
possess arms and be taught alike,
Hi Adrian,
We are aware that some users (not all) experience this problem. We are
looking into it.
-- 73, Joe, K1JT
On 6/10/2015 4:59 PM, PE2K wrote:
Dear OM,
In JT vers X 1.50 i make a transmitting in JT9, but when i do a disable
TX, the transmitting is not stopping but stays on.
Hi Adriaan,
The behaviour of the Enable Tx button has changed slightly in v1.5. It
now toggles on and off automatic transmission. If you turn off automatic
transmission during a transmit period the current transmission will
finish normally. If you wish to interrupt the current transmission
Hi All
From my testing here on both XP and Win7 operating systems the Enable
Tx and Halt Tx buttons do now work as Bill describes. I am using
r5567. I think the confusion arises because the Tx: Message indicator
at the left hand bottom of the main window stays on after Halt Tx is
pressed
Hi All,
I thought I would have a look at the UI with Windows set 125% fonts but
I have hit some issues which I don't believe are related to the display
changes.
I am getting a SIGFPE (floating point exception) when I go to Echo mode.
The offending line is echoplot.cpp line 97. The exception
An additional note...
Clicking Tx Enable from an off (false) state will start a WSPR2
transmission at any point in time during the current 2-minute cycle (per
status bar Tx: .), but only audio is produced if the Tx Enable is
clicked prior to ODD_MIN:30 (ie. 30 seconds into the odd minute).
On 10/06/2015 23:28, Rex wrote:
Hi All
Hi Rex,
From my testing here on both XP and Win7 operating systems the Enable
Tx and Halt Tx buttons do now work as Bill describes. I am using
r5567. I think the confusion arises because the Tx: Message indicator
at the left hand bottom of the main
Hi Joe,
here are a couple of screen shots show the astro window with the
adjustmets below in place:
https://dl.dropboxusercontent.com/u/4192709/astro%2Bdoppler.JPG
https://dl.dropboxusercontent.com/u/4192709/astro-doppler.JPG
the changes between them are just by clicking the Doppler tracking
(Fair warning: I may not be fully awake ...)
I have now reproduced essentially what Eric reported by doing the
following steps:
1. Start WSJT-X in WSPR mode
2. Run a short Tune cycle (click Tune twice)
3. Click Tx Enable
If Step 2 is omitted, I do NOT see what Eric reported. The program
Joe, Steve, et.al.
Yes, I was engaging Tune prior to clicking Tx Enable, generally to
make sure the match on my 630M antenna is alright (very narrow
bandwidth) and that output power is correct for 5W EIRP. It is such a
habit that apparently I do it everytime I start WSJT-X!
I restarted
Hi Eric,
On 6/10/2015 6:49 PM, Eric NO3M wrote:
Having problems with WSPR2 TX here.
WSJTX 1.6.0-devel r5578 (same problems with r5567 also before doing SVN
update/re-compile)
Band: 630m
Tx 1575 Hz
Tx Pct 33%
Upload Spots = true
Band Hopping = false
As soon as I click Tx Enable,
Hi Bill,
Thanks for the suggestions -- please go ahead and commit those changes.
-- Joe
On 6/10/2015 7:44 PM, Bill Somerville wrote:
Hi Joe,
here are a couple of screen shots show the astro window with the
adjustmets below in place:
Hi Joe,
Looked at the astro window a little.
The first top level issue I see is that the layout of the outer QWidget
is not enabled, this means that there is no layout enforced for the
child widgets so they cannot be automatically resized to fit the parent.
Enabling its horizontal layout
Hi Bill
In case it helps I just did a test using PTT switching and PTT does drop
off (as well as the tones) at the time I click Halt TX even though the
TX: message indicator still shows it is TXing.
Rex
On 11/06/2015 8:39 AM, Bill Somerville wrote:
On 10/06/2015 23:28, Rex wrote:
Hi All
On 10/06/2015 23:28, Rex wrote:
Hi All
Hi Rex,
From my testing here on both XP and Win7 operating systems the Enable
Tx and Halt Tx buttons do now work as Bill describes. I am using
r5567. I think the confusion arises because the Tx: Message indicator
at the left hand bottom of the main
Joe, Eric, Bill,
I can reproduce similar behavior as follows. I am using a TS-480.
Let 0:00 (m:ss) be the beginning of a cycle.
Start the program (i.e. issue the command ./wsjtx) some time after 1:00.
Some time between 1:00 and 1:30, press Tune, then press Tune again.
Some time after 1:30, do Tx
On 10/06/2015 16:10, Joe Taylor wrote:
Hi Bill,
Hi Joe,
While testing this I also note that we don't have a setting to allow six
digit grids to be sent. Should we be adding this to WSJT-X as well?
I noticed that, too. Yes, we should do this.
OK, I will have a look at that.
As for the way
Hi Bill
Just to be clear, is the function of the Enable TX and Halt TX in 1.6.0
supposed to be as described in the 1.6.0 User Guide:
Tx toggles the program into automatic T/R sequencing mode and highlights
the button in red. A transmission will start at the beginning of the
selected (odd or
Hi Bill
Yes I am using v1.6.-0-devel, r5567 so this may well be the reason you
can't duplicate it on 1.5. Thus my original comments may not be
relevant to 1.5 on which the issue was originally raised. If so they can
be ignored as it is not a critical issue.
And it does happen with JT9 and
Hi Joe
No windows 125% was used.
The fonts were selected from the buttons that allow users to change Fonts in
Settings - General. I only increased size and bold option. The fonts were
those already offered.
Reason for change - better legibility for slightly visually challenged user.
Charlie
Hi Bill,
While testing this I also note that we don't have a setting to allow six
digit grids to be sent. Should we be adding this to WSJT-X as well?
I noticed that, too. Yes, we should do this.
As for the way we wrap C routines, or otherwise make them callable from
Fortran: you've
Hi Bill,
On Jun 10, 2015, at 9:53 AM, Bill Somerville g4...@classdesign.com wrote:
On 10/06/2015 13:19, Steven Franke wrote:
Bill,
Hi Steve,
I noticed that callsigns retrieved from the hashtable are not being
displayed in the spots window. The callsign is visible in ALL_WSPR.TXT, with
44 matches
Mail list logo
