[wsjt-devel] Enhancement suggestion - TX start time

I've noticed that - at least in FT4/8 - if you enable TX towards the end of a cycle TX starts inmediately despite it won't have the time to transmit something useable. I think it would be helpful if - optionally or not - TX is prevented to start until the next turn when there isn't enough

Re: [wsjt-devel] Enhancement suggestion - 30 second cycles

On 8/5/23 17:00, Reino Talarmo wrote: Sent: sunnuntai 7. toukokuuta 2023 23.29 Why would i talk about non wsjtx usage on a wsjtx group ? It is important to use commonly used words in the same meaning in the ham community. There are many radio amateurs that have used other modes, some even

Re: [wsjt-devel] Enhancement suggestion - 30 second cycles

On 4/27/2023 12:28 PM, Glenn Williams via wsjt-devel wrote: Yes exactly.  After hundreds of QSOs and two+ years that's getting old. But I do really understand the issues with revising good code. Except for contesting, it has ALWAYS been good operating practice to do a LOT more listening than

Re: [wsjt-devel] Enhancement suggestion - 30 second cycles

Yes exactly. After hundreds of QSOs and two+ years that's getting old. But I do really understand the issues with revising good code. --73, Glenn, AF8C On 4/27/2023 12:28 PM, Fred Price wrote: Glenn, Why not just stop the second xmit time sequence by hitting the the Enable Tx or Halt Tx

Re: [wsjt-devel] Enhancement suggestion - 30 second cycles

Hi Glen, I have my TX watchdog set to 3 minutes.  I just let it time out to check my frequency. Larry / W1DYJ On 4/27/2023 12:00, Glenn Williams via wsjt-devel wrote: Good Day, FT8/4 enhancement suggestion follows. (I know that stable code can be broken by side effects and "better is

Re: [wsjt-devel] Enhancement suggestion - 30 second cycles

hat might be hurting the receive of your signals. Let the program do its job and you'll work more! 73 + GL! Bo SM7FJE www.sm7fje.se -Ursprungligt meddelande- Från: Glenn Williams via wsjt-devel Skickat: den 27 april 2023 18:00 Till: wsjt-devel@lists.sourceforge.net Kopia: Glenn William

Re: [wsjt-devel] Enhancement suggestion - 30 second cycles

Glenn, Why not just stop the second xmit time sequence by hitting the the Enable Tx or Halt Tx button? Then re-enable xmit by hitting the Enable Tx for the next sequence you want to xmit. After all you are the control operator for your station. Also then no changes to the code need to be made.

[wsjt-devel] Enhancement suggestion - 30 second cycles

Good Day, FT8/4 enhancement suggestion follows. (I know that stable code can be broken by side effects and "better is the enemy of good enough".) For example, with FT8, instead of having two 15 second transmission cycles per minute, it would be nice to have the option of ONE 15 second

Re: [wsjt-devel] Enhancement Recommendation

--- via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: 29. maaliskuutata 2023 4:08 To: 'WSJT software development' Cc: d...@buckwalter.co Subject: Re: [wsjt-devel] Enhancement Recommendation Yes, during specific events. Since WSJT color codes already indicate if a received CQ

Re: [wsjt-devel] Enhancement Recommendation

to the ‘First’ call, have it respond to the first call that is a new grid as priority over any other responses. Dave Buckwalter From: John Kludt via wsjt-devel Sent: Tuesday, March 28, 2023 1:42 PM To: WSJT software development Cc: John Kludt Subject: Re: [wsjt-devel] Enhancement Recommendation

Re: [wsjt-devel] Enhancement Recommendation

Dave, And just what exactly would be the source of data for grids worked? I frequently work grids via modes other than those in the WSJT-X suite. Or are you proposing that this would apply to only those grids worked within the WSJT-X family of programs during a specific event? When contesting

[wsjt-devel] Enhancement Recommendation

Here's a recommendation for an upgrade: Since the 2.6.0 release you've had the option for CQ response to be 'None', 'First' and 'Max Dist'. How about adding the option to auto respond to 'First New Grid'. This will help when the band is busy and there are multiple responses to your CQ.

Re: [wsjt-devel] Enhancement

Not yet. I need to build a VM for Linux Sent from my iPhone > On Nov 22, 2021, at 6:00 PM, Neil Zampella via wsjt-devel > wrote: > >  > But you do have Gridtracker available for Linux too . > > Neil, KN3ILZ > > On 11/22/2021 2:44 PM, John Korpal wrote: >> One other thing is JTAlert is

Re: [wsjt-devel] Enhancement

But you do have Gridtracker available for Linux too . Neil, KN3ILZ On 11/22/2021 2:44 PM, John Korpal wrote: One other thing is JTAlert is only for windows. Sent from my iPhone On Nov 22, 2021, at 1:42 PM, John Korpal wrote:  I was just following the same design that appends the

Re: [wsjt-devel] Enhancement

On 22/11/2021 15:16, John Korpal via wsjt-devel wrote: My main issue with using an external application to flag message is that application flags a message the user will have to fine that message in WSJTX to take action on the message. My logging program does that today. There is a lag in when

Re: [wsjt-devel] Enhancement

HI! I have done simple list file of US_callsign=state to cqrlog that can be used with wsjtx remote connection. The list is created from file that can be downloaded from fcc (ftp://wirelessftp.fcc.gov/pub/uls/complete/l_amat.zip) holding all information of callsign holders. When US callsign is

Re: [wsjt-devel] Enhancement

If you like more information on me let me know. This is your application and millions use it everyday. You need to make user nothing goes I. To the application that will break it. John (NJ0A) Sent from my iPhone > On Nov 18, 2021, at 11:47 AM, John Korpal wrote: > > Each state is included.

Re: [wsjt-devel] Enhancement

Each state is included. FN32 has five states in that grid. Since we only have the 4 character grid and not the six characters we have a lot of over lap. Check out the screenshot included. Sent from my iPhone > On Nov 18, 2021, at 11:33 AM, Joe Taylor wrote: > > Hi John, > > Thanks for the

Re: [wsjt-devel] Enhancement

Hi John, Thanks for the suggested enhancement. Before we get to more detailed review, perhaps you can describe how you handle 4-character locators that span include more than one US state. -- Joe, K1JT On 11/18/2021 1:12 PM, John Korpal via wsjt-devel wrote: Grid Locator to

Re: [wsjt-devel] Enhancement request — goal posts

Yes Mike ... great improvement - 1524749489046blob.jpg - has my vote. thank you 73 Dwight NS9I On 4/26/2018 8:34 AM, Black Michael via wsjt-devel wrote: Yellow doesn't show up worth a hoot. But perhaps changing the goal posts a bit might help? One option...when they match you see this

[wsjt-devel] Enhancement request #2

 Hi ! As posted here before I made small change to "CQonly" checbox so that toggle of it ON does not run already made decode again, but comes in effect on next decodes. This is desirable with companion programs as re decode sends all stuff to UDP with marked as "new decode" for second time.

Re: [wsjt-devel] Enhancement request

rge.net <mailto:wsjt-devel@lists.sourceforge.net>> *Sent:* Thursday, 26 April 2018 4:57 p.m. *To:* WSJT software development <wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>> *Cc:* Black Michael <mdblac...@yahoo.com <mailto:mdblac...@yahoo.co

Re: [wsjt-devel] Enhancement request — goal posts

Yellow doesn't show up worth a hoot. But perhaps changing the goal posts a bit might help? One option...when they match you see this (could make this look like it does now with equal green/red...just takes a bit more code) When they don't match you see this so it's much more pronounced.  Getting

Re: [wsjt-devel] Enhancement request — goal posts

Hello Michael: I am not comfortable with same color, inverted goal posts in that it is not as easy to discern or remember which one is TX or RX. How about American LaFrance fire engine yellow for RX, officially described as “national safety yellow”. Some refer to it as “lime green”. Many

Re: [wsjt-devel] Enhancement request

2iFB > > From: Black Michael via wsjt-devel <wsjt-devel@lists.sourceforge.net> > Sent: Thursday, 26 April 2018 4:57 p.m. > To: WSJT software development <wsjt-devel@lists.sourceforge.net> > Cc: Black Michael <mdblac...@yahoo.com> > Subject: Re: [wsjt-devel] Enhancement request

Re: [wsjt-devel] Enhancement request

sjt-devel@lists.sourceforge.net> *Cc:* Black Michael <mdblac...@yahoo.com> *Subject:* Re: [wsjt-devel] Enhancement request I played a bit with colors and nothing is really satisfactory. It's an optical thing...with any color right on top of the waterfall there isn't any contrast between the green (

Re: [wsjt-devel] Enhancement request

Sent: Thursday, 26 April 2018 4:57 p.m. To: WSJT software development <wsjt-devel@lists.sourceforge.net> Cc: Black Michael <mdblac...@yahoo.com> Subject: Re: [wsjt-devel] Enhancement request I played a bit with colors and nothing is really satisfactory. It's an optical thing...wi

Re: [wsjt-devel] Enhancement request

I played a bit with colors and nothing is really satisfactory.It's an optical thing...with any color right on top of the waterfall there isn't any contrast between the green (or any other color) and the waterfall. So instead how's this look?  A red box when matched. Or larger red goal posts when

Re: [wsjt-devel] Enhancement request

> On Apr 25, 2018, at 9:36 PM, g...@isect.com wrote: > > I agree with the general point, though, that there are times when it’s nice > to know where the green marker is on the waterfall so a little more contrast > would help. I’ve never had problem finding it. If I did, a glance at the Rx

Re: [wsjt-devel] Enhancement request

so a little more contrast would help. 73 Gary ZL2iFB From: Scott Davis <s...@radiostationexp.net> Sent: Thursday, 26 April 2018 3:14 p.m. To: WSJT software development <wsjt-devel@lists.sourceforge.net> Subject: Re: [wsjt-devel] Enhancement request I'd like to support Dwig

Re: [wsjt-devel] Enhancement request

-- >> From: dgb <n...@bayland.net> <mailto:n...@bayland.net> >> Sent: Thursday, 26 April 2018 7:06 a.m. >> To: wsjt-devel@lists.sourceforge.net >> <mailto:wsjt-devel@lists.sourceforge.net> >> Subject: [wsjt-devel] Enhancement request >>

Re: [wsjt-devel] Enhancement request

For me, too, the green receive marker is harder to see than the red transmit marker. Maybe it would stand out better if it were dark green, blue-green, or blue. Scott W6SDD > On Apr 25, 2018, at 13:06, dgb wrote: > > I'm finding the little green marker for receiving to be

Re: [wsjt-devel] Enhancement request

: wsjt-devel@lists.sourceforge.net Subject: [wsjt-devel] Enhancement request I'm finding the little green marker for receiving to be too small, especially when the waterfall is full of signals. It don't stick out like the red marker. As seconds are critical, spending a second or two to find

Re: [wsjt-devel] Enhancement request

, Gary ZL2iFB -Original Message- From: dgb <n...@bayland.net> Sent: Thursday, 26 April 2018 7:06 a.m. To: wsjt-devel@lists.sourceforge.net Subject: [wsjt-devel] Enhancement request I'm finding the little green marker for receiving to be too small, especially when the waterfall i

[wsjt-devel] Enhancement request

I'm finding the little green marker for receiving to be too small, especially when the waterfall is full of signals. It don't stick out like the red marker. As seconds are critical, spending a second or two to find it can be critical. Would it be possible to increase it's height, like X2?

Re: [wsjt-devel] Enhancement Suggestion - Coloring the "progress bar" to reflect Odd/Even sequence.

Or perhaps have it advance left to right on even sequences and right to left on odd? > On Oct 16, 2016, at 17:02, Björn Ekelund wrote: > > Brilliant idea > > 2016-10-16 22:25 GMT+02:00 Keith Laaks : >> Hi All, >> >> I find that when listening for

[wsjt-devel] Enhancement Suggestion - Coloring the "progress bar" to reflect Odd/Even sequence.

Hi All, I find that when listening for stations, I often need to go glance at the clock to see where we are at that moment with regards to odd/even sequencing. The "progress bar" at the bottom right is a very convenient real-time visualization of the time lapsed/remaining during the current

[wsjt-devel] Enhancement request

Hi, I wonder if an 'always on top' option could be added to the WSJT-X Wide Graph window? Thanks for considering 73 de Guy G4DWV/4X1LT -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop

Re: [wsjt-devel] Enhancement request

Bill Somerville g4wjs@... writes: On 06/03/2015 11:15, John Nelson wrote: Hi Bill, Hi John, Hi Bill and John - I have noticed a similar problem raised by Paul.As Paul points out the DX is used by the dictionary as a DXCC entry. CQ DX !Phillipines In my case,

Re: [wsjt-devel] Enhancement request

On 06/03/2015 11:15, John Nelson wrote: Hi Bill, Hi John, I have noticed a similar problem raised by Paul.As Paul points out the DX is used by the dictionary as a DXCC entry. CQ DX !Phillipines In my case, double-clicking on does not generate a standard message at

Re: [wsjt-devel] Enhancement request

Hi Bill, I have noticed a similar problem raised by Paul.As Paul points out the DX is used by the dictionary as a DXCC entry. CQ DX !Phillipines In my case, double-clicking on does not generate a standard message at all. This is not the same result as seen by Paul who

Re: [wsjt-devel] Enhancement request

On 06/03/2015 07:05, Paul DU2/WA8UGN wrote: Bill Somerville g4wjs@... writes: Hi Bill and all - Hi Paul, On 06/03/2015 00:09, Eric NO3M wrote: Hi Eric, I ran into a similar situation with the following message: CQ NO3M DX CQ DX NO3M

Re: [wsjt-devel] Enhancement request

Bill Somerville g4wjs@... writes: CQ DX NO3M is the correct form and is a standard message form, you can add your locator as well just like a normal CQ call. Thanks for that Bill, that will do the trick. 73 de Guy G4DWV/4X1LT

Re: [wsjt-devel] Enhancement request

Sounds like you have Disable TX after sending 73 checked in File/Settings/General. Mike W9MDB From: Guy [mailto:g...@drteeth.co.uk] Sent: Thursday, March 05, 2015 3:05 PM To: wsjt-devel@lists.sourceforge.net Subject: [wsjt-devel] Enhancement request I am not a programmer at all

Re: [wsjt-devel] Enhancement request

Michael Black mdblack98@... writes: Sounds like you have Disable TX after sending 73 checked in File/Settings/General. I do, but standard CQ calls go out okay indefinitely and custom ones do not. The Disable after 73 setting is the same in both cases. The expected behaviour is that both

[wsjt-devel] Enhancement request

I am not a programmer at all, but I do follow this list and find what I read fascinating even though I don't understand it. I currently use the 1.3 release and it has a behaviour that I find annoying and I wonder if it has been addressed in either 1.4 or 1.5. When sending a custom CQ

Re: [wsjt-devel] Enhancement request

On 05/03/2015 22:07, Guy G4DWV/4X1LT wrote: Hi Guy, Michael Black mdblack98@... writes: Sounds like you have Disable TX after sending 73 checked in File/Settings/General. I do, but standard CQ calls go out okay indefinitely and custom ones do not. The Disable after 73 setting is the same

Re: [wsjt-devel] Enhancement request

I ran into a similar situation with the following message: CQ NO3M DX to keep stateside callers from answering. I had assumed the CQ would have been picked up and TX Enable persist after each invocation. However, that was not the case. I saw other DX stations at the time using the same

Re: [wsjt-devel] Enhancement request

On 06/03/2015 00:09, Eric NO3M wrote: Hi Eric, I ran into a similar situation with the following message: CQ NO3M DX CQ DX NO3M is the correct form and is a standard message form, you can add your locator as well just like a normal CQ call. Note that this only works with CQ CQ DX QRZ or

Re: [wsjt-devel] Enhancement request

Excellent... will try it later when 160 wakes up. Thanks for the info! 73 Eric NO3M On 03/05/2015 07:30 PM, Bill Somerville wrote: On 06/03/2015 00:09, Eric NO3M wrote: Hi Eric, I ran into a similar situation with the following message: CQ NO3M DX CQ DX NO3M is the correct form and is a

Re: [wsjt-devel] Enhancement request

On 6/03/2015 11:09 AM, Eric NO3M wrote: perhaps something JT-Alert does for them? Of course, JT-Alert is not able to run on *nix, so that's not an option here. No. JTAlert doesn't play with the TX settings of WSJT-X. de Laurie VK3AMA

Re: [wsjt-devel] Enhancement request

Bill Somerville g4wjs@... writes: Hi Bill and all - On 06/03/2015 00:09, Eric NO3M wrote: Hi Eric, I ran into a similar situation with the following message: CQ NO3M DX CQ DX NO3M is the correct form and is a standard message form, you