On 11/11/2015 04:41, Michael Black wrote:
Hi Mike,
Thanks...can you do this for 1.6.1 too?
That is Joe's branch, he merges in changes from the trunk on a regular
basis.
If you want to grab the change in your workspace you simply have to do:
$ svn merge -c 6071 ^/branches/wsjtx
then rebuil
Thanks...can you do this for 1.6.1 too?
73
Mike W9MDB
On Tue, Nov 10, 2015 at 5:28 PM, Bill Somerville
wrote:
> On 10/11/2015 23:10, Bill Somerville wrote:
> > That is a reproducible issue. The double-click decode processing is
> > not checking what mode is selected (mode in the mode menu) and s
On 10/11/2015 23:10, Bill Somerville wrote:
> That is a reproducible issue. The double-click decode processing is
> not checking what mode is selected (mode in the mode menu) and simply
> doing what it would in dual mode.
I have committed a change to the development branch (1.6.0) to stop this
h
On 10/11/2015 22:56, Michael Black wrote:
Hi Mike,
OK...try this...I just did this one.
Had a current JT9 CQ pop up.
Changed mode to JT65.
Double clicked the JT9 CQ
Transmit started doing JT9
That is a reproducible issue. The double-click decode processing is not
checking what mode is selected
OK...try this...I just did this one.
Had a current JT9 CQ pop up.
Changed mode to JT65.
Double clicked the JT9 CQ
Transmit started doing JT9
Mode button still shows JT65. Waterfall shows JT9 appropriately.
Shouldn't the mode button change?
On Tue, Nov 10, 2015 at 4:38 PM, Bill Somerville
wrote:
On 10/11/2015 22:15, Michael Black wrote:
Hi Mike,
YesI can repeat this at will with that sequence. You don't see
that behavior?
Going either JT9->JT65 or the other way.
It may be that too much time has elapsed of the current period and
WSJT-X is refusing to change the message as it is to
On 10/11/2015 22:15, Michael Black wrote:
Hi Mike,
YesI can repeat this at will with that sequence. You don't see
that behavior?
Going either JT9->JT65 or the other way.
I have just build ^/branches/wsjtx_exp r6059 and cannot reproduce this.
I tried both with auto enable TX and without.
YesI can repeat this at will with that sequence. You don't see that
behavior?
Going either JT9->JT65 or the other way.
73
Mike W9MDB
On Tue, Nov 10, 2015 at 4:06 PM, Bill Somerville
wrote:
> On 10/11/2015 22:02, Michael Black wrote:
>
> Hi Mike,
>
> I may have missed an inferred step.
> #1
On 10/11/2015 22:02, Michael Black wrote:
Hi Mike,
I may have missed an inferred step.
#1 Start a transmit on JT9
#2 Halt
#3 Double-click on JT65 event
Still stays in JT9 mode.
That's not intended, is it? I don't recall previously ever having to
touch the mode button unless I was CQ'ing and c
I may have missed an inferred step.
#1 Start a transmit on JT9
#2 Halt
#3 Double-click on JT65 event
Still stays in JT9 mode.
That's not intended, is it? I don't recall previously ever having to touch
the mode button unless I was CQ'ing and changing mode.
Mike W9MDB
On Tue, Nov 10, 2015 at 3:4
On 10/11/2015 21:47, Bill Somerville wrote:
Further restrictions are applied if you have QSY while transmittingset
in the settings
Should have said *unset*
73
Bill
G4WJS.
--
On 10/11/2015 21:41, Michael Black wrote:
Hi Mike,
> 1.6.1 r6058
>
> #1 Start a transmit on JT9.
> #2 Double-click a JT65 entry in either window
>
> Mode does not switch to JT65
This is the intended behaviour. The message content should not change
either. The transmit setup is only done at he sta
1.6.1 r6058
#1 Start a transmit on JT9.
#2 Double-click a JT65 entry in either window
Mode does not switch to JT65
Next transmit will be JT9 instead of JT65 (as expected since mode doesn't
switch).
Same behavior going the other way too.
Mike W9MDB
---
13 matches
Mail list logo
