[wsjt-devel] Experimental changes in r8146

2017-09-30 Thread AB1NJ

Joe, r8146 working very good for me now, thanks!


Hi all,

Changes in program behavior can be confusing, so I apologize for some
recent instability in GUI operational behavior.  Code revision r8146 is
yet another attempt to get it right -- or as near "right" as possible --
while supporting both simplex and split-frequency default operating styles.



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] Experimental changes in r8125 & 8144

2017-09-29 Thread AB1NJ
Using 8144 here now.  I don't usually post a lot, but I feel as if I 
have to say something now. Concerning these changes...I really think that:


1) it is now overly complicated, and

2) it worked better before.

I always have been one of those that never checked the LockTX=RX box, 
and liked the way it used to work. That being, if I saw someone CQ and 
clicked on their call, it would move the RX and TX to their offset. AND, 
when I would CQ, if someone called me off my offset, my TX would stay in 
place so that I could work split. All was good. Now, if I see someone 
calling CQ, answer on their offset, have QSO, and then finish and go to 
call another, my TX stays on the first stations offset QRMing them 
unless I remember to CTRL-Click on the new station. This is tough for an 
old dog to remember in the heat of battle, and I have already 
inadvertently QRMed others. Now, with 8144, we have a setting that will 
set TX and RX freq together, but doing that takes away the former fine 
feature of ALT-Click or SHIFT-click. So I've lost my well liked features 
with 8144. No problem for me now, as I just go back to my trusty 8080, 
but I'm hoping the changes to 8144 will not end up in RC3 or whatever 
comes next.


In the past I have suggested just doing away with the LockTX=RX box and 
be done with it, and I still think that is the best option. Watching 
this and other lists I see how many times the same questions are asked 
and answered. I can only imagine how many such questions will be posed 
if these changes become permanent. That is my feedback.


Rob AB1NJ


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


[wsjt-devel] RC2 release date?

2017-08-25 Thread AB1NJ
Just wondering about release of RC2 time frame?  It has been awhile 
since RC1 was released and there have been many advances in the program. 
So many so, that it is kind of obvious when someone is using RC1, which 
is noticeably "deaf" compared to recent revisions. Many of us are hoping 
that a RC2 will be available to the masses soon, so that things become 
more uniform.  Thanks, Rob AB1NJ



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


[wsjt-devel] Lock TX=RX checkbox

2017-08-06 Thread AB1NJ
I know it is near the release of RC2, but I hope you will reconsider 
removing the Lock TX=RX checkbox altogether. It seems that most run with 
it on, and by calling offset, they end up moving to the caller's QRG 
rather than staying put. With the importance of calling offset with FT8, 
it makes this issue more important. If it were just gone, that would be 
the best solution for all.


Rob AB1NJ


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


[wsjt-devel] adding a "skip TX1" checkbox

2017-07-20 Thread AB1NJ
I see the discussion on the RR73, but possibly more important is a easy 
way to skip TX1 message, in order to send a report (normally TX2) on 
first reply to CQ instead of grid. A checkbox would be obvious 
solution.  Thoughts?


Rob AB1NJ

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] Ver 1.8 RC1 audio in slider problem

2017-07-19 Thread AB1NJ
I vote to get rid of the slider once and for all. I'm tired of reading 
about it, as I'm sure people are tired of answering the same question 
over and over again.


Rob AB1NJ

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel