Re: [wsjt-devel] Request for WSJT-X Feature

2020-06-29 Thread Dave AA6YQ
+ AA6YQ comments below Dave, Sorry I have to step in here. > Seriously, I do think Ham Radio software does need to adopt some modern > architecture principles. ABSOLUTE GARBAGE in my opinion ... that attitude puts Amateur Radio and its people back into the stone age + That's not my po

Re: [wsjt-devel] Request for WSJT-X Feature

2020-06-29 Thread Adrian
"a pair of equal and oppositely charged or magnetized poles separated by a distance." Is the 'equal' referring to the amount of 'charge' applied to both poles rather than length ? It certainly could be interpreted that way, rather than assume 'equal' length of the 'poles'. In that context Th

Re: [wsjt-devel] Request for WSJT-X Feature

2020-06-29 Thread Dave AA6YQ
+ AA6YQ comments below On the first point, we more or less agree. A development team can focus on many things, true. The point Im trying to make here is that logging and weak-signal processing are two very different functions, and don't belong in the same application. If an exception is to be ma

Re: [wsjt-devel] Request for WSJT-X Feature

2020-06-29 Thread Robert A. Klahn (AD6I)
> Perhaps this is a subject better for a QRZ forum? I agree. I drifted off list topic. Im going to stop answering, and will move to QRZ. I absolutely agree with Steve's comments on the quality of WSJT-X and Hamlib, and associate myself with his comments. See you on QRZ. Thanks. Robert. AD6I.

Re: [wsjt-devel] Request for WSJT-X Feature

2020-06-29 Thread Stephen VK3SIR
Dave, Sorry I have to step in here. > Seriously, I do think Ham Radio software does need to adopt some modern > architecture principles. ABSOLUTE GARBAGE in my opinion ... that attitude puts Amateur Radio and its people back into the stone age You move away from standards you get uncon

Re: [wsjt-devel] Request for WSJT-X Feature

2020-06-29 Thread Robert A. Klahn (AD6I)
Dave: On the first point, we more or less agree. A development team can focus on many things, true. The point Im trying to make here is that logging and weak-signal processing are two very different functions, and don't belong in the same application. If an exception is to be made here, yes, it

Re: [wsjt-devel] Request for WSJT-X Feature

2020-06-29 Thread Dave AA6YQ
+ AA6YQ comments below Seriously, I do think Ham Radio software does need to adopt some modern architecture principles. In this context the WSJT-X team should be focused on weak-signal communication protocol processing. Issues such as logging should be left to others to focus on, and there shoul

Re: [wsjt-devel] Request for WSJT-X Feature

2020-06-29 Thread Al Pawlowski
I ran FD with N3FJP (the FD version) and N3FJP logged just fine from JTalert (you enable ACLog in JTalert) - and never got the duplicate logs that went into WSJTx’s contest log because I did not recognize the caller fast enough and was using auto-log. Both N3FJP and JTalert were on the same mach

Re: [wsjt-devel] Request for WSJT-X Feature

2020-06-29 Thread Robert A. Klahn (AD6I)
My apologies to all for my reply coming with some extra snark. Seriously, I do think Ham Radio software does need to adopt some modern architecture principles. In this context the WSJT-X team should be focused on weak-signal communication protocol processing. Issues such as logging should be l

Re: [wsjt-devel] Request for WSJT-X Feature

2020-06-29 Thread Stephen VK3SIR
Terry, Matters around TCP spotting has been raised a number of times (and I note a subsequent response from Robert AD6I). Terry - as Bill raises - JTAlert is by FAR the most advanced tool that has the "potential" ... yet at the moment lacks "capability". [ Laurie VK3AMA also runs his own "sp

Re: [wsjt-devel] Request for WSJT-X Feature

2020-06-29 Thread Robert A. Klahn (AD6I)
IMHO, this sort of thing is often better implemented as a program emulating the client's supported protocol. That program can then communicate with whatever downstream service is needed, in its preferred protocol. Even better is to apply some well defined modern application solution instead, li

Re: [wsjt-devel] Request for WSJT-X Feature

2020-06-29 Thread Bill Somerville
On 30/06/2020 01:53, Terry Estes wrote: Many other amateur radio stations use the N3FJP Logging Software, primarily for logging ARRL Field Day and Winter Field Day contests. The addition of Field Day exchange capabilities to WSJT-X has made the use during FD of FT-8 a major improvement and has i

[wsjt-devel] Request for WSJT-X Feature

2020-06-29 Thread Terry Estes
Many other amateur radio stations use the N3FJP Logging Software, primarily for logging ARRL Field Day and Winter Field Day contests. The addition of Field Day exchange capabilities to WSJT-X has made the use during FD of FT-8 a major improvement and has increased its use for FD. Many stations now

Re: [wsjt-devel] FT8: Double Click, sometimes wrong CallSign

2020-06-29 Thread roland.hartmann
Hi Reino, I am trying it. Until now it seems to work – thanks ! 73 Roland, DK4RH Von: Reino Talarmo Gesendet: Montag, 29. Juni 2020 19:26 An: 'WSJT software development' Betreff: Re: [wsjt-devel] FT8: Double Click, sometimes wrong CallSign Hi Roland, You could try use General >

Re: [wsjt-devel] FT8: Double Click, sometimes wrong CallSign

2020-06-29 Thread Gary McDuffie
> On Jun 29, 2020, at 11:25, Reino Talarmo wrote: > > Sometimes I try to answer a CQ with a double click in the Band Activity Part > - but not the station is used, which I had selected. More than likely, you are a victim of the multiple decoding cycles per 15 second sequence. The screen up

Re: [wsjt-devel] Feature Modification please

2020-06-29 Thread Alan
Separate box (or status bar entry) that just displays the highest row number? Alan G0TLK On 29 June 2020 19:21:45 Bill Somerville wrote: On 29/06/2020 19:12, Gerald Smith wrote: Good Afternoon, After working Field Day this weekend, and operating on the FT4 - FT8 station, I noticed that in th

Re: [wsjt-devel] Feature Modification please

2020-06-29 Thread Bill Somerville
On 29/06/2020 19:12, Gerald Smith wrote: Good Afternoon, After working Field Day this weekend, and operating on the FT4 - FT8 station, I noticed that in the Contest Log the QSOs are numbered in the left hand column, numbers ascending from the top of the log to the bottom. By the same token,

[wsjt-devel] Feature Modification please

2020-06-29 Thread Gerald Smith
Good Afternoon, After working Field Day this weekend, and operating on the FT4 - FT8 station, I noticed that in the Contest Log the QSOs are numbered in the left hand column, numbers ascending from the top of the log to the bottom. By the same token, each new QSO is added to the top of the li

Re: [wsjt-devel] FT8: Double Click, sometimes wrong CallSign

2020-06-29 Thread Reino Talarmo
Hi Roland, You could try use General > Display Start new period decodes at top. At least I got help. 73, Reino OH3mA From: roland.hartm...@web.de [mailto:roland.hartm...@web.de] Sent: 29. kesäkuuta 2020 19:24 To: 'WSJT software development' Subject: [wsjt-devel] FT8: Double Click, sometimes

[wsjt-devel] FT8: Double Click, sometimes wrong CallSign

2020-06-29 Thread roland.hartmann
Think a smaller issue, but also happened on other stations: Sometimes I try to answer a CQ with a double click in the Band Activity Part - but not the station is used, which I had selected. Example: I did a double click on IU8MOA - but N9FN was used. It is almost happened, if somethin

Re: [wsjt-devel] Feature Request

2020-06-29 Thread Bill Somerville
On 29/06/2020 03:47, Jim Brown wrote: There are times when it could be quite helpful to be able to switch special operating features on and off from the main operating window. One of those times occurred this weekend, when I wanted to be able to switch between FD messages to work FD stations an

Re: [wsjt-devel] iNVALIDE DATA

2020-06-29 Thread Bill Somerville
Hi Matt, you can log these callers or ignore them, to log them you will have to guess their FD section which may be possible with a bit of help from QRZ.COM. You can bet 1D is their FD class. If they are DX there's no issue, just use "1D DX", I suppose you could use "1D DX" for all of them an