Re: [wsjt-devel] Unexpected Behavior

2019-03-03 Thread Claude Frantz

On 3/2/19 7:35 PM, Tag Loomis (Tag) wrote:

Hi Tag,

I wouldn't consider it a bug, more of a known action, but I could be 
wrong of course.


It's probably a feature.

It would be interesting to see if our expected behaviour can be 
performed with Ctrl and double click, if I understand well point 
10.1.9.2 in Special Mouse Commands of the user guide.


Best wishes,
Claude (DJ0OT)


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] Unexpected Behavior

2019-03-02 Thread Tag Loomis (Tag)
I've noticed that if I double-click on the callers "CQ" is the only way to
jump to their TX frequency.. IfI click on anything thing else, such as a
reply, my TX doesn't move.

I wouldn't consider it a bug, more of a known action, but I could be wrong
of course.




On Sat, Mar 2, 2019 at 3:09 AM Claude Frantz 
wrote:

> On 1/20/19 4:50 AM, Frank Kirschner wrote:
>
> Hi Frank & all,
>
> > First thing I noticed was that when I double-clicked on his call in the
> > Band Activity window, it wasn't made the active call. The last call I
> > worked stayed in the transmit messages list. So I manually entered his
> > call. It seemed to transmit the first message OK. However, every few
> > minutes, either the active call in the transmit messages window would
> > switch back to the previous call, or the QRG would jump to 3.573 MHz. I
> > switched back and transmitted some more, but this kept happening.
>
> I'm not sure if this is the subject pointed on previously.
>
> Please allow me to explain my observation, in order to verify.
>
> I'm on FT8 mode. A have performed and terminated a QSO with a first
> station. Now, a second station is calling me on another frequency. The
> entry appears with a red background colour. I double click on this entry
> in order to respond to this second calling station. The green RX marker
> jumps to the frequency of the calling station, but the red TX marker
> remains in place although "Hold TX Freq" is OFF. Therefore I'm now
> transmitting on the previous frequency where my first partner station is
> still working.
>
> Bug or feature ? This behaviour was present in 2.0.0 and is still
> present in 2.0.1. If I remember well, this behaviour has the reported
> previously here.
>
> Best wishes,
> Claude (DJ0OT)
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] Unexpected Behavior

2019-03-02 Thread Claude Frantz

On 1/20/19 4:50 AM, Frank Kirschner wrote:

Hi Frank & all,

First thing I noticed was that when I double-clicked on his call in the 
Band Activity window, it wasn't made the active call. The last call I 
worked stayed in the transmit messages list. So I manually entered his 
call. It seemed to transmit the first message OK. However, every few 
minutes, either the active call in the transmit messages window would 
switch back to the previous call, or the QRG would jump to 3.573 MHz. I 
switched back and transmitted some more, but this kept happening.


I'm not sure if this is the subject pointed on previously.

Please allow me to explain my observation, in order to verify.

I'm on FT8 mode. A have performed and terminated a QSO with a first 
station. Now, a second station is calling me on another frequency. The 
entry appears with a red background colour. I double click on this entry 
in order to respond to this second calling station. The green RX marker 
jumps to the frequency of the calling station, but the red TX marker 
remains in place although "Hold TX Freq" is OFF. Therefore I'm now 
transmitting on the previous frequency where my first partner station is 
still working.


Bug or feature ? This behaviour was present in 2.0.0 and is still 
present in 2.0.1. If I remember well, this behaviour has the reported 
previously here.


Best wishes,
Claude (DJ0OT)


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] Unexpected Behavior

2019-01-20 Thread Claude Frantz

On 1/20/19 4:50 AM, Frank Kirschner wrote:

Hi Frank & all,

I was trying to work 9LY1JM on 80 m FT8. QRG was 3.567 MHz, which I have 
in the frequencies list for FT8.  His audio offset was 355 Hz.


First thing I noticed was that when I double-clicked on his call in the 
Band Activity window, it wasn't made the active call. The last call I 
worked stayed in the transmit messages list.

The same observation here.

Best wishes,
Claude (DJ0OT)


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] Unexpected Behavior

2019-01-19 Thread Bill Frantz
Their call does not meet the requirements for a compressed call 
in wsjt-x. (One or two character prefix, his is 3 characters). 
So their call frequently goes out in a 13 character general text 
message which doesn't work when you double click it. My formula 
for working them is:


He is running Fox and Hound mode as a Fox, so call him from at 
least 1000 Hz above the frequency listed on their web page.


When he comes back to you, you will not receive a signal report. 
Instead you will receive something like, "AE6JV 9LY2JM ". (If 
you have a 4 character call you will get, " 9LY2JM -".


When you receive this message select the TX 3 message and change 
your transmit frequency to below 1000 Hz.


Eventually you should receive a RR73 and a prompt to log the 
QSO. If you don't receive the RR73, I would manually log the QSO 
and see if it appears on Clublog.


73 Bill AE6JV

On 1/19/19 at 7:50 PM, frank.kirsch...@gmail.com (Frank 
Kirschner) wrote:



I was trying to work 9LY1JM on 80 m FT8. QRG was 3.567 MHz, which I have in
the frequencies list for FT8.  His audio offset was 355 Hz.

First thing I noticed was that when I double-clicked on his call in the
Band Activity window, it wasn't made the active call. The last call I
worked stayed in the transmit messages list. So I manually entered his
call. It seemed to transmit the first message OK. However, every few
minutes, either the active call in the transmit messages window would
switch back to the previous call, or the QRG would jump to 3.573 MHz. I
switched back and transmitted some more, but this kept happening.

I tried it both in Fox/Hound mode and standard mode with the same results.

He did eventually answer me, but I had to keep manually entering his call
and bringing the VFO back to the correct frequency.

Any ideas?

73,
Frank
KF6E


-
Bill Frantz| When it comes to the world | Periwinkle
(408)356-8506  | around us, is there any choice | 16345 
Englewood Ave
www.pwpconsult.com | but to explore? - Lisa Randall | Los Gatos, 
CA 95032




___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


[wsjt-devel] Unexpected Behavior

2019-01-19 Thread Frank Kirschner
I was trying to work 9LY1JM on 80 m FT8. QRG was 3.567 MHz, which I have in
the frequencies list for FT8.  His audio offset was 355 Hz.

First thing I noticed was that when I double-clicked on his call in the
Band Activity window, it wasn't made the active call. The last call I
worked stayed in the transmit messages list. So I manually entered his
call. It seemed to transmit the first message OK. However, every few
minutes, either the active call in the transmit messages window would
switch back to the previous call, or the QRG would jump to 3.573 MHz. I
switched back and transmitted some more, but this kept happening.

I tried it both in Fox/Hound mode and standard mode with the same results.

He did eventually answer me, but I had to keep manually entering his call
and bringing the VFO back to the correct frequency.

Any ideas?

73,
Frank
KF6E
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


[wsjt-devel] Unexpected Behavior - Halt TX

2018-12-01 Thread Robert Rearden
During last night's roundup, I had unexpected behavior of the HALT TX button.  
On two occasions HALT TX failed to stop the Tx sequence even though the HALT TX 
button was clicked during the first 2 or 3 seconds of the Tx/Rx sequence. AUTO 
SEQ was on at the time. Tx continued to the end of the normal Tx portion of the 
sequence and then halted. I operate on an iMac computer (late 2015) using Mac 
OS 10.14.1.

Robert Rearden
ae...@att.net




___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel