!
-Tim Carlson (KD0GYG)
> On Sep 28, 2017, at 4:19 PM, James Shaver <n2...@windstream.net> wrote:
>
> It took a bit of a higher-than-usual concentration of caffeine for me to snap
> into it but after that, I have begun to really like it.
>
> Jim S.
> N2ADV
>
the developers. Thank you!
-Tim KD0GYG
> On Jul 18, 2017, at 4:47 PM, Bill Somerville <g4...@classdesign.com> wrote:
>
> On 18/07/2017 23:18, Tim Carlson wrote:
>> I would expect that to be handled automatically. Otherwise we should
>> reliable the checkbox “
Seq”. :)
-Tim KD0GYG
> On Jul 18, 2017, at 4:10 PM, Bill Somerville <g4...@classdesign.com> wrote:
>
> On 18/07/2017 22:56, Tim Carlson wrote:
>> Not sure how it’s QRM to try to finish the Auto Seq. If the other guy’s
>> Auto Seq keeps sending “RRR”, why should’t I tr
Thanks, Gary - I didn’t see that option and haven’t tried it.
-Tim KD0GYG
> On Jul 18, 2017, at 3:44 PM, Gary McDuffie <mcduf...@ag0n.net> wrote:
>
>
>> On Jul 18, 2017, at 11:26 AM, Tim Carlson <t...@widehf.com> wrote:
>>
>> OK, I get it - if the o
Not sure how it’s QRM to try to finish the Auto Seq. If the other guy’s Auto
Seq keeps sending “RRR”, why should’t I try to reply with another “73” to
complete the sequence? I only operate on HF at this point, and during the QSO,
that frequency is only shared by two QSO partners, isn’t it?
, uh, get rid
> of said coffee), pet the cat, feed the kids, etc and keep sending 73 over and
> over. I disable Auto after my report goes out and switch to manual to prevent
> the situation you describe :)
>
> 73!
> Jim S.
> N2ADV
>
>> On Jul 18, 2017, at 10:56 AM,
Hi All,
I have a general question about Auto Seq when answering a CQ call.
Out of 78 completed QSO’s with FT8 and Auto Seq, at least a dozen of them (when
I’m answering a CQ) end with me sending “73” which disables my Auto Tx, then
receiving another “RRR”. I have to then scramble and click
gn.com> wrote:
>
> On 11/07/2017 19:12, Tim Carlson wrote:
>> Would you consider that the first signal on the left is being overdriven
>> somewhat? Or is that just a consequence of a stronger signal? Or is it
>> some atmospheric condition causing the signal to spread
Sometime between building and running the latest update and installing
v1.8.0-rc1 r7847 (on OS X), the frequencies for my only named configuration all
disappeared. The default configuration still has all the frequencies, so I
cloned it and reset my preferences.
I’ve always let the IARU Region
I tried this, but I get a compile error. The one item I changed in
mainwindow.ui looks like this:
htmlhead/bodypChecktoenableautomaticsequencingofTxmessagesbasedonreceivedmessages./p/body/html
I agree - I suspected it might be a Qt issue, and it is pretty minor.
Thanks for the feedback!
-Tim
> On Jul 10, 2017, at 11:11 AM, John Nelson wrote:
>
> Hi Bill,
>
>> I'm not sure we can do anything about it, it is a matter for the Qt
>> developers.
>
> In that case,
The tool tips on OS X are inconsistent - most of the time they cut off part of
the text, but if you move the mouse back and forth over the control, eventually
they do show the whole text.
These examples are from r7836.
Cut off text:
Good text:
This isn't a new issue - the same thing
Hi Joe,
I agree with John - using r7836, it worked great for three QSO’s I just made.
This makes it MUCH easier to get a QSO going - thanks!
One surprise was that it responded to a Tx1 made off-frequency compared to my
CQ call, but when I think about it that should be the correct behavior.
Thank you, Michael. I’ve been confused as to the function of the slider - it
never seemed to do anything for me because I’ve always left Flatten checked.
It seems like education is needed in either case (leaving it on the main
window, or moving it to the waterfall window). In that case, it
checked the wsjtx_log.adi and wsjtx.log files to confirm that they don’t
contain the second QSO (that I was not prompted to log). ALL.TXT has
everything, of course, but not in a nice adi format.
Thanks!
-Tim Carlson (KD0GYG
(rather than
3.9.0-rc5), everything complied without issues.
-Tim (KD0GYG)
> On Jul 1, 2017, at 9:41 PM, Tim Carlson <t...@widehf.com> wrote:
>
> Also, here’s my configuration results:
>
> $ FC=gfortran-mp-5 cmake -D
> CMAKE_PREFIX_PATH="~/Qt3/5.9.1/clang_64;~
d the “Could NOT find OpenMP_C" and OpenMP_CXX lines - does that
have anything to do with the subsequent error?
-Tim
> On Jul 1, 2017, at 9:20 PM, Bill Somerville <g4...@classdesign.com> wrote:
>
> On 02/07/2017 03:49, Tim Carlson wrote:
>> Thanks, Bill. That did cause it to
<g4...@classdesign.com> wrote:
>
> On 01/07/2017 22:22, Tim Carlson wrote:
>> I’m following the instructions here
>> <https://sourceforge.net/p/wsjt/wsjt/HEAD/tree/branches/wsjtx/INSTALL> and
>> everything works fine up until the build of wsjtx (revision 7770). It is
>&
0.11.6), Qt 5.9.1, latest MacPorts, latest Cmake
(installed from dmg - 3.9.0-rc5).
Any suggestions would be appreciated.
Thanks!
-Tim Carlson (KD0GYG)--
Check out the vibrant tech community on one of the world's most
en
I just made my first FT8 QSO with WB4KDI as well. I agree - very cool.
-Tim - KD0GYG
> On Jun 29, 2017, at 6:43 PM, C. Gary Rogers wrote:
>
> Just made first FT8 QSO with WB4KDI…Way cool!!!…73 Gary
>
>> On Jun 29, 2017, at 7:56 PM, Dave 'Doc' Corio
20 matches
Mail list logo