Re: [wsjt-devel] SUGGESTION

Re: [wsjt-devel] SUGGESTION My suggestion would be to default the Tune to 30 seconds (some tuners are slow) and then have CTRL-Click make it stick. Mike W9MDB On Sunday, March 6, 2022, 06:10:13 AM CST, Reino Talarmo via wsjt-devel mailto:wsjt-devel@lists.sourceforge.net>> wrote: I al

Re: [wsjt-devel] SUGGESTION

73 de Uwe DG2YCB Von: Reino Talarmo via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Gesendet: Montag, 7. März 2022 06:03 An: 'WSJT software development' Cc: Reino Talarmo Betreff: Re: [wsjt-devel] SUGGESTION >Then let's make it switchable.The majority of us

Re: [wsjt-devel] SUGGESTION

>Then let's make it switchable.The majority of users will certainly find a Tune >watchdog useful and want to have it activated, but those who don't like it can >then simply switch it off. Good solution. Hi Uwe, How that new Tune watchdog will interact with the current Tx watchdog? 1. Would

Re: [wsjt-devel] SUGGESTION

Hi, How about some sort of split button where the primary option is for 30 seconds and via the secondary option folks can select to have it on until they switch it off. MW - VK3TIN, AJ6EI On Mon, Mar 7, 2022 at 8:11 AM Gary McDuffie via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: >

Re: [wsjt-devel] SUGGESTION

n: Carey Fisher via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Gesendet: Sonntag, 6. März 2022 14:26 An: WSJT software development Cc: Carey Fisher Betreff: Re: [wsjt-devel] SUGGESTION Uh, no! On Sat, Mar 5, 2022 at 11:51 PM Gavin ZL3GAV via wsjt-devel wrote: Hello Not a huge priority,

Re: [wsjt-devel] SUGGESTION

Thanks for the suggestions. Gary N8GT Sent from my iPhone > On Mar 6, 2022, at 1:09 PM, Gary McDuffie via wsjt-devel > wrote: > >  > >> On Mar 5, 2022, at 21:19, Gavin ZL3GAV via wsjt-devel >> wrote: >> >> With the TUNE button, can this be limited to timeout at 10 seconds maximum >> plea

Re: [wsjt-devel] SUGGESTION

> On Mar 6, 2022, at 02:56, Alan via wsjt-devel > wrote: > > it's an important feature because many XCVR's do not offer this function in > a simple manner. Put the radio in CW mode and lock the key. Simple. Gary - AG0N ___ wsjt-devel mailing l

Re: [wsjt-devel] SUGGESTION

> On Mar 5, 2022, at 21:19, Gavin ZL3GAV via wsjt-devel > wrote: > > With the TUNE button, can this be limited to timeout at 10 seconds maximum > please? > > From experience, we all make silly mistakes, whilst tuning my FT-991A I got > distracted, with the result, I nuked the radio (since

Re: [wsjt-devel] SUGGESTION

eforge.net] > *Gesendet:* Sonntag, 6. März 2022 19:29 > *An:* WSJT software development > *Cc:* Carey Fisher > *Betreff:* Re: [wsjt-devel] SUGGESTION > > > > Make it a programmable (up to 10 minutes) time, default to 2 minutes. > > > > On Sun, Mar 6, 2022

Re: [wsjt-devel] SUGGESTION

From: Daniel Delaplain via wsjt-devel Sent: Monday, 7 March 2022 07:46 To: careyfis...@gmail.com; WSJT software development Cc: Daniel Delaplain Subject: Re: [wsjt-devel] SUGGESTION The tune time out is programmable. Go to file/settings/general. At the bottom of the screen is Tx watchdog

Re: [wsjt-devel] SUGGESTION

My thought is if you need that much time to tune the radio to the antenna, fix the antenna and feed line to it. Bruce WA1YZN On 3/6/2022 13:45, Daniel Delaplain via wsjt-devel wrote: The tune time out is programmable.  Go to file/settings/general. At the bottom of the screen is Tx watchdog. It

Re: [wsjt-devel] SUGGESTION

The tune time out is programmable.  Go to file/settings/general. At the bottom of the screen is Tx watchdog. It works for both the Enable Tx button, and the Tune button. Mine is set for 4 minutes.  Sent from AT&T Yahoo Mail on Android On Sun, Mar 6, 2022 at 10:30 AM, Carey Fisher via wsjt-

Re: [wsjt-devel] SUGGESTION

The tune time out is programmable.  Go to file/settings/general. At the bottom of the screen is Tx watchdog. It works for both the Enable Tx button, and the Tune button. Mine is set for 4 minutes.  Sent from AT&T Yahoo Mail on Android On Sun, Mar 6, 2022 at 5:06 AM, Black Michael via wsjt-

Re: [wsjt-devel] SUGGESTION

Cc: Carey Fisher Betreff: Re: [wsjt-devel] SUGGESTION Make it a programmable (up to 10 minutes) time, default to 2 minutes. On Sun, Mar 6, 2022 at 12:19 PM DG2YCB, Uwe via wsjt-devel wrote: Hi all, Since I had similar requests for such a function in the past, I already programmed a

Re: [wsjt-devel] SUGGESTION

ssions. > > > > 73 de Uwe, DG2YCB > > > > *Von:* Carey Fisher via wsjt-devel [mailto: > wsjt-devel@lists.sourceforge.net] > *Gesendet:* Sonntag, 6. März 2022 14:26 > *An:* WSJT software development > *Cc:* Carey Fisher > *Betreff:* Re: [wsjt-devel] SUGGESTION

Re: [wsjt-devel] SUGGESTION

sions. > > > > 73 de Uwe, DG2YCB > > > > *Von:* Carey Fisher via wsjt-devel [mailto: > wsjt-devel@lists.sourceforge.net] > *Gesendet:* Sonntag, 6. März 2022 14:26 > *An:* WSJT software development > *Cc:* Carey Fisher > *Betreff:* Re: [wsjt-devel] SUGGESTION > &

Re: [wsjt-devel] SUGGESTION

: Carey Fisher via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Gesendet: Sonntag, 6. März 2022 14:26 An: WSJT software development Cc: Carey Fisher Betreff: Re: [wsjt-devel] SUGGESTION   Uh, no!   On Sat, Mar 5, 2022 at 11:51 PM Gavin ZL3GAV via wsjt-devel wrote: Hello   Not a

Re: [wsjt-devel] SUGGESTION

enough to tune your antenna, but it effectively prevents unwanted continuous transmissions. 73 de Uwe, DG2YCB Von: Carey Fisher via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Gesendet: Sonntag, 6. März 2022 14:26 An: WSJT software development Cc: Carey Fisher Betreff: Re: [wsjt-devel

Re: [wsjt-devel] SUGGESTION

Uh, no! On Sat, Mar 5, 2022 at 11:51 PM Gavin ZL3GAV via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Hello > > > > Not a huge priority, but one of those nice to have please… > > > > With the TUNE button, can this be limited to timeout at 10 seconds maximum > please? > > > > From exper

Re: [wsjt-devel] SUGGESTION

My suggestion would be to default the Tune to 30 seconds (some tuners are slow) and then have CTRL-Click make it stick. Mike W9MDB On Sunday, March 6, 2022, 06:10:13 AM CST, Reino Talarmo via wsjt-devel wrote: I also belong to the continuous carrier lot. Already now there is the TX

Re: [wsjt-devel] SUGGESTION

I also belong to the continuous carrier lot. Already now there is the TX watch dog that can be set from 1 min to 99 min or disabled. I assume that the 1 min value could be good enough in most cases for those who don't want boil their rig.. The 1 min value seems to be maximum 1 min time depending w

Re: [wsjt-devel] SUGGESTION

I also share the opinion that continuous tune is useful. I used it to provide a steady signal for adjusting my LF phasing exciter to balance out the opposite sidebands. That process can take several minutes and should be rechecked occasionally. 73, Paul N1BUG On 3/6/22 04:39, Claude Frantz v

Re: [wsjt-devel] SUGGESTION

I agree that a continuous carrier ability is useful for testing, and also agree that a timeout would be a good idea in case of distractions etc - it unfortunately happens. Maybe a small selection of timeout periods in program settings, including no timeout, with a default at say 1 minute might

Re: [wsjt-devel] SUGGESTION

On 3/6/22 10:28, Charles Suckling via wsjt-devel wrote: Hi Charly & all, I personally find it useful to be able to generate a continuous carrier with WSJT-X using the Tune button. I share this opinion, it's an important feature because many XCVR's do not offer this function in a simple man

Re: [wsjt-devel] SUGGESTION

Gavin, Tony et al I personally find it useful to be able to generate a continuous carrier with WSJT-X using the Tune button. 73 Charlie DL3WDG On Sun, 6 Mar 2022 at 10:13, Tony ZL3HAM via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > A good idea Gavin and I don't think it would be to

Re: [wsjt-devel] SUGGESTION

A good idea Gavin and I don't think it would be too difficult to do, we're keep our fingers crossed. A very warm day today. 73 Tony On 6/03/2022 5:29 pm, Gavin ZL3GAV via wsjt-devel wrote: Not a huge priority, but one of those nice to have please… With the TUNE button, can this be limited

[wsjt-devel] SUGGESTION

Not a huge priority, but one of those nice to have please… With the TUNE button, can this be limited to timeout at 10 seconds maximum please? >From experience, we all make silly mistakes, whilst tuning my FT-991A I got >distracted, with the result, I nuked the radio (since fixed) runni

[wsjt-devel] SUGGESTION

Hello Not a huge priority, but one of those nice to have please. With the TUNE button, can this be limited to timeout at 10 seconds maximum please? >From experience, we all make silly mistakes, whilst tuning my FT-991A I got distracted, with the result, I nuked the radio (since fixed) r

Re: [wsjt-devel] Suggestion for Q65 Astronomical Data table

Hi Lance, On 10/17/2021 12:05 AM, Lance Collister, W7GJ via wsjt-devel wrote: As I am currently on an EME DXpedition without any access to internet or a reliable GPS puck that runs on Windows 10, it occurred to me that it should be very easy to add a very helpful item to the Astronomical Data

Re: [wsjt-devel] Suggestion for Q65 Astronomical Data table

On 10/19/2021 09:10, Reino Talarmo via wsjt-devel wrote: Its there already, labelled as Delay. Hi Charlie, You may talk about totally different issue. User Guide states: delay of your own EME echoes in seconds The problem is accurate time. A correct DT is only possible, when a time refere

Re: [wsjt-devel] Suggestion for Q65 Astronomical Data table

MNI TNX! On 10/19/2021 09:10, Reino Talarmo via wsjt-devel wrote: Its there already, labelled as Delay. Hi Charlie, You may talk about totally different issue. User Guide states: delay of your own EME echoes in seconds The problem is accurate time. A correct DT is only possible, when a ti

Re: [wsjt-devel] Suggestion for Q65 Astronomical Data table

Its there already, labelled as Delay. Hi Charlie, You may talk about totally different issue. User Guide states: delay of your own EME echoes in seconds The problem is accurate time. A correct DT is only possible, when a time reference is available in some form. One less accurate metho

Re: [wsjt-devel] Suggestion for Q65 Astronomical Data table

Hi Lance Its there already, labelled as Delay. 73 Charlie DL3WDG On Tue, 19 Oct 2021 at 00:30, Lance Collister, W7GJ via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > As I am currently on an EME DXpedition without any access to internet or > a reliable GPS puck that runs on Windows 1

[wsjt-devel] Suggestion for Q65 Astronomical Data table

As I am currently on an EME DXpedition without any access to internet or a reliable GPS puck that runs on Windows 10, it occurred to me that it should be very easy to add a very helpful item to the Astronomical Data table. If the correct DT were shown, I could make computer clock adjustments us

Re: [wsjt-devel] Suggestion re OpenSSL

Steve, that's not possible, the OpenSSL libraries are controlled by US state and federal export restrictions on strong cryptography. The end user must obtain them themselves and take note if the restrictions apply to them. We do not, nor wish to, restrict the ability of international Amateur

[wsjt-devel] Suggestion re OpenSSL

Hi Gents, As a suggestion is it possible to direct the installer scripts on a Windows build to auto-deploy the Appropriate Win32 or Win64 OpenSSL Lite package? Should the SDK's and package requirements be looked at with regards to providing access to these libraries available for the future? I

Re: [wsjt-devel] Suggestion: Have Rx following Tx on CQ option?

Ps: I meant "previous contact" not "precious contact" ! Typnoing is bbbaaaddd and too much coffee this morning here ! -Original Message- From: Stephen Ireland Sent: Wednesday, 13 May 2020 11:00 AM To: WSJT software development Subject: Re: [wsjt-devel] Suggestion:

Re: [wsjt-devel] Suggestion: Have Rx following Tx on CQ option?

le Sent: Wednesday, 13 May 2020 8:39 AM To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] Suggestion: Have Rx following Tx on CQ option? On 12/05/2020 23:24, Stephen Ireland wrote: > Folks, > > One minor suggestion for future RC candidates... I have been calling a > station

Re: [wsjt-devel] Suggestion: Have Rx following Tx on CQ option?

Um ... all I do is click on the DOWN ARROW next to the Tx location which sets the Rx to the same location.  One click. Neil, KN3ILZ On 5/12/2020 6:24 PM, Stephen Ireland wrote: Folks, One minor suggestion for future RC candidates... I have been calling a station XQ1KN that cannot see me ... s

Re: [wsjt-devel] Suggestion: Have Rx following Tx on CQ option?

On 12/05/2020 23:24, Stephen Ireland wrote: Folks, One minor suggestion for future RC candidates... I have been calling a station XQ1KN that cannot see me ... so I have aborted attempts and clicked on Tx6 to return to calling CQ. I have Hold Tx Frequency set ... but the Rx has not returned wi

[wsjt-devel] Suggestion: Have Rx following Tx on CQ option?

Folks, One minor suggestion for future RC candidates... I have been calling a station XQ1KN that cannot see me ... so I have aborted attempts and clicked on Tx6 to return to calling CQ. I have Hold Tx Frequency set ... but the Rx has not returned with me to the frequency that I am calling on.

Re: [wsjt-devel] Suggestion: CW ID callsign

Agree on all.  When running in a contest I never go more than three contacts without giving my call, but usually go at least two unless conditions are dicey and I don't want anyone on the other end to have to wait through a couple of contacts before deciding whether they want to work me or no

Re: [wsjt-devel] Suggestion: CW ID callsign

On 10/20/2019 2:44 PM, David Gilbert wrote: As best I know, you don't need to ID every contact, and I suspect you wouldn't even if moving around within a bandwidth as narrow as is typical for FT8. Far too much attention to identification is paid by those who don't operate much, and/or aren't

Re: [wsjt-devel] Suggestion: CW ID callsign

Hi Dave, Thanks for the response. If a call sign is specified in Settings which is not compliant with the requirements of the 28-bit encoding scheme, my recollection is that with WSPR the non-compliant callsign will code into some kind of nonsense in the *digital* message. In any case, a non-comp

Re: [wsjt-devel] Suggestion: CW ID callsign

assigned call sign on its transmitting channel at the end of each communication…” AK2L *From:*David Gilbert *Sent:* Sunday, October 20, 2019 14:44 *To:* wsjt-devel@lists.sourceforge.net *Subject:* Re: [wsjt-devel] Suggestion: CW ID callsign As best I know, you don't need to ID every contac

Re: [wsjt-devel] Suggestion: CW ID callsign

Ahh ... OK. Well, I don't normally use WSPR but I just switched to it and it let me enter a rather length string of gibberish for a callsign.  And at the bottom right of the Settings - General page it lets me set an interval for a periodic CW ID ... which I assume would be the same gibberish

Re: [wsjt-devel] Suggestion: CW ID callsign

And I think this would also be an issue for FT8 and other modes in jurisdictions (not those administered by the United States Federal Communications Commission) where station identification using the digital mode is not compliant and CW Morse identification is required.

Re: [wsjt-devel] Suggestion: CW ID callsign

, 2019 14:44 To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] Suggestion: CW ID callsign As best I know, you don't need to ID every contact, and I suspect you wouldn't even if moving around within a bandwidth as narrow as is typical for FT8. So why not simply use the f

Re: [wsjt-devel] Suggestion: CW ID callsign

Hi Dave, the specific actual situation I have encountered involves using WSJT-X for WSPR (not FT8). Your thoughts? David / K7DB On Sun, Oct 20, 2019, 2:50 PM David Gilbert wrote: > > As best I know, you don't need to ID every contact, and I suspect you > wouldn't even if moving around within a

Re: [wsjt-devel] Suggestion: CW ID callsign

As best I know, you don't need to ID every contact, and I suspect you wouldn't even if moving around within a bandwidth as narrow as is typical for FT8.  So why not simply use the freeform 13-character TX5 message to periodically ID?  I've played around with it a bit and it will even accept a

[wsjt-devel] Suggestion: CW ID callsign

Hi friends, I am writing to share an idea... WSJT callsign encoding generally accommodates most amateur radio callsigns, but some callsigns -- e.g., some special-event callsigns, and callsigns which might use a *four character suffix* as provided at ITU RR19-7 §30

Re: [wsjt-devel] Suggestion

Hi! Yes, I agree with the usefulness of combining a switch for the FT4 / FT8. I find in this addition the usefulness of the function! Unfortunately, there may be an inconvenience in synchronization: the RX FT8 may be different from the RX FT4 (i it had such an RX-SWL). This fact should be noted

Re: [wsjt-devel] Suggestion

Hi Joe, Thank you for your answer. Cheers Serge On 09/08/2019 00:36, Joe Taylor wrote: Hi Serge, On 8/8/2019 17:31, Serge F6BHK wrote: at the dawn of WSJT-X we had the choice to decode JT65+JT9 under the same combo value. I remember I found it very useful. When I double-clicked a JT65 sig

Re: [wsjt-devel] Suggestion

Hi Serge, On 8/8/2019 17:31, Serge F6BHK wrote: at the dawn of WSJT-X we had the choice to decode JT65+JT9 under the same combo value. I remember I found it very useful. When I double-clicked a JT65 signal then I was sending using JT65, same for JT9. would'nt it be nice to have a FT8+FT4 comb

[wsjt-devel] Suggestion

Hi all! at the dawn of WSJT-X we had the choice to decode JT65+JT9 under the same combo value. I remember I found it very useful. When I double-clicked a JT65 signal then I was sending using JT65, same for JT9. would'nt it be nice to have a FT8+FT4 combo value that decode both of the protoco

[wsjt-devel] SUGGESTION: Display or not, confirmed QSOs

Joe (and the team), First, the last (new) rev of WSJT-X is WAY FASTER to decode a busy band. THANK YOU! My suggestion: Because I made thousands of FT8 contacts (especially on 20m, 30m and 40m), a huge amount of the CQ decodes on a busy band are GREEN (confirmed QSO for call/band/etc). Even if

Re: [wsjt-devel] Suggestion for Additional Checkbox

On 25 Apr 2019 at 14:30, Bill Somerville wrote: > Frank, > > WSJT-X tries to prevent *Fox* FT8 DXpedition mode stations from > operating on the "usual" FT8 frequencies. Clearly we cannot stop use of > Fox mode if the DX does not use CAT control. Other programs like MSHV > allow a mode similar

Re: [wsjt-devel] Suggestion for Additional Checkbox

Bravo! 73 -Jim NU0C On Thu, 25 Apr 2019 18:02:35 -0400 James Shaver wrote: > No CAT control with this old rig (picture attached) and it holds its own ;) > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.ne

Re: [wsjt-devel] Suggestion for Additional Checkbox

No CAT control with this old rig (picture attached) and it holds its own ;) > On Apr 25, 2019, at 5:07 PM, Jim Shorney wrote: > > > The point was that CAT is not essential in any case. The notion that CAT is > *required* to use FT/JT modes is a myth propagated by those who don't know > any

Re: [wsjt-devel] Suggestion for Additional Checkbox

The point was that CAT is not essential in any case. The notion that CAT is *required* to use FT/JT modes is a myth propagated by those who don't know any better. There are those of us who do not use CAT for whatever reason and we appreciate the ability to operate this way. To successfully to

Re: [wsjt-devel] Suggestion for Additional Checkbox

Bill, Thanks for the info. I'm an old CW op at heart, and even with a PhD in EE, I sometimes scratch my head trying to figure out why the software works the way it does. 73, Frank KF6E On Thu, Apr 25, 2019 at 9:54 AM Bill Somerville wrote: > On 25/04/2019 14:15, Frank Kirschner wrote: > > Some

Re: [wsjt-devel] Suggestion for Additional Checkbox

On 25/04/2019 14:15, Frank Kirschner wrote: Someone wrote that the software prevented using Hound mode in the regular band segments. I was just demonstrating that this was not the case. I didn't actually transmit, since I saw no stations in Fox mode. Frank, WSJT-X tries to prevent *Fox* FT8

Re: [wsjt-devel] Suggestion for Additional Checkbox

On Tue, Apr 23, 2019 at 10:49 PM Jim Shorney wrote: > On Tue, 23 Apr 2019 14:11:19 +0100 > "Martin Davies G0HDB" wrote: > > > The use of Split is all-but essential for slick operation in Hound mode, > which is presumably > > why the software complained if you changed to a Hound configuration > w

Re: [wsjt-devel] Suggestion for Additional Checkbox

Martin, Thanks for you complete reply. I appreciate your taking the time. My comments are below. On Tue, Apr 23, 2019 at 9:20 AM Martin Davies G0HDB wrote: > > Frank: > > If the station you want to work is concurrently transmitting multiple > (typically 3) signals 60Hz > apart, and conducting m

Re: [wsjt-devel] Suggestion for Additional Checkbox

On Tue, 23 Apr 2019 14:11:19 +0100 "Martin Davies G0HDB" wrote: > The use of Split is all-but essential for slick operation in Hound mode, > which is presumably > why the software complained if you changed to a Hound configuration without > one or other of > the Split options being selected.

Re: [wsjt-devel] Suggestion for Additional Checkbox

On 22 Apr 2019 at 17:22, Frank Kirschner wrote: > OK. How do I tell whether it's a F/H mode station or a "derivative" > program? Most of the time, when I switch to F/H mode to work DX, I am able > to work them. Does that indicate the DX station is, indeed, running F/H? Frank: If the station you

Re: [wsjt-devel] Suggestion for Additional Checkbox

If you're answering on the normal FT8 frequencies, its not the WSJT-X DXPedition mode which specifically locks out the standard FT8 frequencies. They are using a third-party software that I referred to previously. Neil, KN3ILZ On 4/22/2019 5:22 PM, Frank Kirschner wrote: Grant, On Sun, Apr 21

Re: [wsjt-devel] Suggestion for Additional Checkbox

I don't know of many people who 'toggle' F/H mode.   As has been pointed out, if you're using F/H mode, you're chasing a DXPedition that has normally announced what frequencies it will be using, and would not be on the normal FT8 locations. Whoever is using a F/H look-alike on the normal frequenc

Re: [wsjt-devel] Suggestion for Additional Checkbox

Just found my reading glasses and noticed that it is 10.131, not 10.136, so that's not an example. But that has noting to do with the point of improving the user interface. I created hundreds of databases for industry and government, and found that they were best-received when the most used funct

Re: [wsjt-devel] Suggestion for Additional Checkbox

On Sun, Apr 21, 2019 at 5:51 PM Martin Davies G0HDB wrote: > On 21 Apr 2019 at 13:47, Frank Kirschner wrote: > > I use a specific, separate configuration for F/H mode and see no need to > have a main-screen > check-box to select the mode; as has already been pointed out selecting > that, and any

Re: [wsjt-devel] Suggestion for Additional Checkbox

way, click the waterfall to set the green marker, or right >> click to set the red marker – simple, intuitive and easy. >> >> >> >> 73 GL >> >> Gary ZL2iFB >> >> >> >> *From:* Frank Kirschner >> *Sent:* 22 April 2019 05:38 &

Re: [wsjt-devel] Suggestion for Additional Checkbox

On Sun, Apr 21, 2019 at 7:08 PM Jim Shorney wrote: > On Mon, 22 Apr 2019 08:06:26 +0930 > "Grant VK5GR" wrote: > > > Fox and Hound was never in the main FT8 channels – indeed I believe > Bill, Frank Joe and the team coded the system to not let you run F/H mode > on the main FT8 channels. > > > .

Re: [wsjt-devel] Suggestion for Additional Checkbox

Grant, On Sun, Apr 21, 2019 at 6:40 PM Grant VK5GR wrote: > Frank, > > > > Fox and Hound was never in the main FT8 channels – indeed I believe Bill, > Frank Joe and the team coded the system to not let you run F/H mode on the > main FT8 channels. > Interesting. If that's the case, that function

Re: [wsjt-devel] Suggestion for Additional Checkbox

On Sun, Apr 21, 2019 at 5:51 PM Martin Davies G0HDB wrote: > On 21 Apr 2019 at 13:47, Frank Kirschner wrote: > > > I've been a user of FT8 F/H mode since its inception and I can't recall > any instances where > *genuine* F/H signals have appeared in the standard FT8 band segments; can > anyone >

Re: [wsjt-devel] Suggestion for Additional Checkbox

Also, by the way, click the waterfall to set the green marker, or right > click to set the red marker – simple, intuitive and easy. > > > > 73 GL > > Gary ZL2iFB > > > > *From:* Frank Kirschner > *Sent:* 22 April 2019 05:38 > *To:* WSJT software development

Re: [wsjt-devel] Suggestion for Additional Checkbox

On Mon, 22 Apr 2019 08:06:26 +0930 "Grant VK5GR" wrote: > Fox and Hound was never in the main FT8 channels – indeed I believe Bill, > Frank Joe and the team coded the system to not let you run F/H mode on the > main FT8 channels. which can easily be subverted by not using CAT control of

Re: [wsjt-devel] Suggestion for Additional Checkbox

of mixing F/H mode with standard FT8 traffic. Regards, Grant VK5GR From: Frank Kirschner [mailto:frank.kirsch...@gmail.com] Sent: Monday, 22 April 2019 3:18 AM To: WSJT software development Subject: Re: [wsjt-devel] Suggestion for Additional Checkbox On Sat, Apr 20, 2019 at 11

Re: [wsjt-devel] Suggestion for Additional Checkbox

At one point the controls for F/H were on the main part of the GUI and the group was flooded with questions asking why they were receiving and transmitting “funny” because they were inadvertently checking the box when it was on the main page. That went away when the box was moved into the settin

Re: [wsjt-devel] Suggestion for Additional Checkbox

On 21 Apr 2019 at 13:47, Frank Kirschner wrote: > That's not completely accurate. Initially, most F/H operation was in the > regular band segment, but as those segments filled up, DX stations moved to > the alternate frequencies. I have worked DX stations in F/H mode in the > regular band segments

Re: [wsjt-devel] Suggestion for Additional Checkbox

F2 is your friend. If 'Advanced" was the last active tab you you will be right there. That's a single key stroke! What's so hard about that? 73 -Jim NU0C On Sun, 21 Apr 2019 13:38:24 -0400 Frank Kirschner wrote: > On Sat, Apr 20, 2019 at 10:53 PM WB5JJJ wrote: > > > F/H is not something

Re: [wsjt-devel] Suggestion for Additional Checkbox

!) he calls us. Also, by the way, click the waterfall to set the green marker, or right click to set the red marker – simple, intuitive and easy. 73 GL Gary ZL2iFB From: Frank Kirschner Sent: 22 April 2019 05:38 To: WSJT software development Subject: Re: [wsjt-devel] Suggestion for

Re: [wsjt-devel] Suggestion for Additional Checkbox

On Sat, Apr 20, 2019 at 11:19 PM Neil Zampella wrote: > There is already a F/H mode, safely placed where it can't be > accidentally checked as the old VHF contest box (at least I believe it > was the VHF contest) was at one point. > > The suggestion has been to clone your current FT8 configuratio

Re: [wsjt-devel] Suggestion for Additional Checkbox

On 21/04/2019 18:38, Frank Kirschner wrote: As I pointed out, it wouldn't clutter the screen. There is ample room for several more checkboxes. Frank, that is not correct, there are other controls that are not always visible. Here is a view of the UI design file that shows what is really the

Re: [wsjt-devel] Suggestion for Additional Checkbox

On Sat, Apr 20, 2019 at 10:53 PM WB5JJJ wrote: > F/H is not something you would normally select on a frequent basis, > Yes it is. I mostly do DX hunting, and around 10 to 15% of my QSOs have been in F/H mode. Normally, I never respond to CQs from band-entities that I already have confirmed on Lo

Re: [wsjt-devel] Suggestion for Additional Checkbox

> On Apr 20, 2019, at 15:46, Frank Kirschner wrote: > > Between the Hold Tx Freq checkbox and the Call 1st checkbox, there is room > for several more checkboxes. One I would suggest is Fox/Hound mode. I would > also suggest this automatically set Split to either Rig or Fake It, which > coul

Re: [wsjt-devel] Suggestion for Additional Checkbox

Or just hit F2 and you are one or two mouse clicks away... 73 -Jim NU0C On Sat, 20 Apr 2019 21:48:03 -0500 WB5JJJ wrote: > F/H is not something you would normally select on a frequent basis, so a > check box cluttering the main screen is not necessary. > > As previously suggested setting a

Re: [wsjt-devel] Suggestion for Additional Checkbox

There is already a F/H mode, safely placed where it can't be accidentally checked as the old VHF contest box (at least I believe it was the VHF contest) was at one point. The suggestion has been to clone your current FT8 configuration, and set up the frequencies in that clone to the DXPedition fr

Re: [wsjt-devel] Suggestion for Additional Checkbox

F/H is not something you would normally select on a frequent basis, so a check box cluttering the main screen is not necessary. As previously suggested setting a Configuration for that mode (and others) are just 2 clicks away and totally customizable. This procedure is outlined in the User Manual

Re: [wsjt-devel] Suggestion for Additional Checkbox

Good idea. I'm not familiar enough with the program to have thought of that. Thanks. 73, Frank KF6E On Sat, Apr 20, 2019 at 6:16 PM N3SL wrote: > Just a suggestion - works for me: Create a F/H "configuration" and toggle > to it. Two mouse clicks. > > On Sat, Apr 20, 2019 at 4:50 PM Frank Kirs

[wsjt-devel] Suggestion for Additional Checkbox

Between the Hold Tx Freq checkbox and the Call 1st checkbox, there is room for several more checkboxes. One I would suggest is Fox/Hound mode. I would also suggest this automatically set Split to either Rig or Fake It, which could be selected somewhere else. If the menus are turned off, it takes a

Re: [wsjt-devel] Suggestion regarding colors

For MacOS, this is taken care by JT-Bridge. Robert Rearden AE5UV _ On Dec 22, 2018, at 8:41 AM, Tom Ramberg via wsjt-devel wrote: May I suggest using JTAlert which has already taken care of this? 73 de Tom OH6VDA > 22. des. 2018 kl. 00:17 skrev I Z : > > Suggestion reg

Re: [wsjt-devel] Suggestion regarding colors

May I suggest using JTAlert which has already taken care of this? 73 de Tom OH6VDA > 22. des. 2018 kl. 00:17 skrev I Z : > > Suggestion regarding colors. > I really love what was done in 2.0. Finally a great logger, many thanks! > I miss one enhancement though. When I see a message from one stat

[wsjt-devel] Suggestion regarding colors

Suggestion regarding colors. I really love what was done in 2.0. Finally a great logger, many thanks! I miss one enhancement though. When I see a message from one station to another (without CQ or my call), it is in white. It will be very nice if the second call in this message was highlighted,

Re: [wsjt-devel] Suggestion Hold TX Freq sticky

I did and Laurie said the same thing. I gave it a try just now and it DOES work. I guess there was just a glitch in my configurations when the FT8 RU was in progress. That was the last time I did a configuration change. That weekend, I had to restart JTAlert every time I went back to normal FT8.

Re: [wsjt-devel] Suggestion Hold TX Freq sticky

Sorry. It seems to be working now. I just tried it. However, it did not function properly when I tried the FT8 Round Up a couple weekend back. This could have just been a glitch that day in my computer. Thanks. On Mon, Dec 17, 2018 at 2:25 PM Laurie, VK3AMA <_vk3a...@vkdxer.net> wrote: > > On

Re: [wsjt-devel] Suggestion Hold TX Freq sticky

On 18/12/2018 4:19 am, WB5JJJ wrote: If I do a configuration change, I have to stop and restart JTAlert as it doesn't connect again automatically to the new configuration. That's OK when I go to DXP configuration since I will probably stay there for several hours. That should not be the ca

Re: [wsjt-devel] Suggestion Hold TX Freq sticky

No, I haven't. It's not that big of a deal to me when I go to/from DXP. It's just become habit, like checking the Hold box when going from MSK144 to FT8 - most times. On Mon, Dec 17, 2018 at 11:31 AM Bill Somerville wrote: > On 17/12/2018 17:19, WB5JJJ wrote: > > If I do a configuration change

Re: [wsjt-devel] Suggestion Hold TX Freq sticky

On 17/12/2018 17:19, WB5JJJ wrote: If I do a configuration change, I have to stop and restart JTAlert as it doesn't connect again automatically to the new configuration. Hi George, that's not right, several versions ago changes were made to the WSJT-X UDP protocol and to JTAlert to make confi

Re: [wsjt-devel] Suggestion Hold TX Freq sticky

Yes, I do that for DXP and such that require several changes. But just to change modes, there is a drop down for that already that's just 2 clicks and everything continues along just fine. Plus the Auto Seq and Call 1st are sticky already. If I do a configuration change, I have to stop and resta

Re: [wsjt-devel] Suggestion Hold TX Freq sticky

On 17/12/2018 15:21, WB5JJJ wrote: As I change from MSK144 to FT8, the vast majority of the time I forget to check the Hold Tx Freq box until I've moved off my clear spot. Could this box be made a sticky for either choice? Hi George, one easy option is to create a separate configuration for

  1   2   >