click moves Rx, ctl-click moves both, shift click moves Tx.  I knew
> something moved them both...and sometimes I hit control instead of shift in
> the heat of he moment.
>

I think it would be better user interface design to have "move Rx" be left
click and "move Tx" to be right click, so those basic functions can each be
done with one hand. But that's another topic.

Do you have any theories on why a station gets covered by another station
> on exactly the same frequuency +/- 1-2 Hz?
>

I don't know, maybe the other station chose that frequency because it
looked clear to transmit (the weak station was weak enough that they didn't
see it). On a crowded FT8 segment, like 14.074 in the evening here, signals
are packed in like sardines and you have to do your best to find a
relatively open slot.

Or maybe he was just a lid! But IMHO it's going to be futile to try to
eliminate liddish behavior through software.

73, Paul K6PO


> On Sat, Apr 20, 2019 at 2:05 AM Paul Kube <[email protected]> wrote:
>
>> Jeff,
>>
>>
>>> What I think is happening is that people click on signals so they can
>>> see them in the Rx Frequency window.  They have not checked the Hold Tx
>>> Frequency and so the transmitter frequency is automatically following the
>>> Rx frequency.
>>>
>>
>> Are you talking about single-clicking in the waterfall? That only moves
>> the Rx frequency, whether or not Hold Tx Freq is checked.
>>
>> 73, Paul K6PO
>>
>>
>>> On Thu, Apr 18, 2019 at 4:41 PM James Shaver <[email protected]> wrote:
>>>
>>>> And speaking of S/N, I just realized this is the “devel” reflector and
>>>> not the generic WSJT Group reflector.  This really isn’t a topic suitable
>>>> for the development side, to be honest...
>>>>
>>>> 73,
>>>>
>>>> Jim S.
>>>> N2ADV (ex KD2BIP)
>>>>
>>>> > On Apr 18, 2019, at 4:34 PM, James Shaver <[email protected]> wrote:
>>>> >
>>>> > It never ceases to amaze me how so many hams instantly jump to the
>>>> conclusion that what they witness on the air is automatically attributed to
>>>> intentional “rudeness” or ill intent.
>>>> >
>>>> > His s/n is not really relevant - it’s very possible that even if
>>>> propagation was, to coin a phrase, putting this person in your lap, that
>>>> does not mean you’re even a weak trace on his/her end. That person may have
>>>> a very high local noise floor due to an indoor antenna or a lot of noisy
>>>> consumer electronics around them or it could even be as simple as plain old
>>>> propagation differences or it could be someone who has just jumped into
>>>> digital modes for the very first time and is not yet familiar with the
>>>> interface.
>>>> >
>>>> > If it bothers you that much, look up their email on QRZ and send them
>>>> a screen shot and *politely* ask if they even heard/saw you. If they
>>>> didn’t, offer to help them track down local noise generators or help them
>>>> optimize their receive setup.
>>>> >
>>>> > It pays to give people the benefit of the doubt. If they turn out to
>>>> be a jerk, then you can at least walk away with the satisfaction that you
>>>> tried your best to be an “Elmer” and are, at the end of the day, the better
>>>> person.
>>>> >
>>>> > And relax. It’s just ham radio. Nobody died on the table. This is
>>>> supposed to be fun.
>>>> >
>>>> > Jim S.
>>>> > N2ADV
>>>> >
>>>> > _______________________________________________
>>>> > wsjt-devel mailing list
>>>> > [email protected]
>>>> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>>>
>>>>
>>>> _______________________________________________
>>>> wsjt-devel mailing list
>>>> [email protected]
>>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>>>
>>> _______________________________________________
>>> wsjt-devel mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>>
>> _______________________________________________
>> wsjt-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>
> _______________________________________________
> wsjt-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to