Yes Mike ... great improvement - 1524749489046blob.jpg - has my vote.
thank you 73 Dwight NS9I
On 4/26/2018 8:34 AM, Black Michael via wsjt-devel wrote:
Yellow doesn't show up worth a hoot.
But perhaps changing the goal posts a bit might help?
One option...when they match you see this (could
ay, 26 April 2018 4:57 p.m.
*To:* WSJT software development <mailto:wsjt-devel@lists.sourceforge.net>>
*Cc:* Black Michael mailto:mdblac...@yahoo.com>>
*Subject:* Re: [wsjt-devel] Enhancement request
I played a bit with colors and nothing is really satisfactory.
It's an
Just got the same , but was slower to implement it :)
I made green a little bit darker (could be still little darker) and
raised the hook one pix (actually cutted one pix from bottom).
Cute to play with, as no dx here up 61°N and 6m is also closed.
--
Saku
OH1KH
Black Michael via wsjt-dev
Yellow doesn't show up worth a hoot.
But perhaps changing the goal posts a bit might help?
One option...when they match you see this (could make this look like it does
now with equal green/red...just takes a bit more code)
When they don't match you see this so it's much more pronounced. Getting t
Hello Michael:
I am not comfortable with same color, inverted goal posts in that it is not
as easy to discern or remember which one is TX or RX. How about American
LaFrance fire engine yellow for RX, officially described as “national safety
yellow”. Some refer to it as “lime green”.
Many t
gt; Sent: Thursday, 26 April 2018 4:57 p.m.
> To: WSJT software development
> Cc: Black Michael
> Subject: Re: [wsjt-devel] Enhancement request
>
> I played a bit with colors and nothing is really satisfactory.
> It's an optical thing...with any color right on top of the wat
through it, please.
Well, that’s just a suggestion to throw in the pot, Sorry I can’t
actually code it!
73,
Gary ZL2iFB
*From:* Black Michael via wsjt-devel
*Sent:* Thursday, 26 April 2018 4:57 p.m.
*To:* WSJT software development
*Cc:* Black Michael
*Subject:* Re: [wsjt-devel] Enhancement
: WSJT software development
Cc: Black Michael
Subject: Re: [wsjt-devel] Enhancement request
I played a bit with colors and nothing is really satisfactory.
It's an optical thing...with any color right on top of the waterfall there
isn't any contrast between the green (or any other
I played a bit with colors and nothing is really satisfactory.It's an optical
thing...with any color right on top of the waterfall there isn't any contrast
between the green (or any other color) and the waterfall.
So instead how's this look? A red box when matched.
Or larger red goal posts when
> On Apr 25, 2018, at 9:36 PM, g...@isect.com wrote:
>
> I agree with the general point, though, that there are times when it’s nice
> to know where the green marker is on the waterfall so a little more contrast
> would help.
I’ve never had problem finding it. If I did, a glance at the Rx Fr
n the waterfall so a little more contrast
would help.
73
Gary ZL2iFB
From: Scott Davis
Sent: Thursday, 26 April 2018 3:14 p.m.
To: WSJT software development
Subject: Re: [wsjt-devel] Enhancement request
I'd like to support Dwight's comment again. How well the FT8 receive ma
I'd like to support Dwight's comment again. How well the FT8 receive marker
stands out is a fine point for sure. But I think there are good reasons to
want to find it quickly. Sometimes it happens that another operator and I have
a contact going, and he has sent me a good signal report -- let
For me, too, the green receive marker is harder to see than the red transmit
marker. Maybe it would stand out better if it were dark green, blue-green, or
blue.
Scott
W6SDD
> On Apr 25, 2018, at 13:06, dgb wrote:
>
> I'm finding the little green marker for receiving to be too small, especia
Hi Gary and you are right in actual use of the application. It's just a
visual thing with these old eyes I guess! ;-)
73 Dwight NS9I
On 4/25/2018 3:54 PM, g...@isect.com wrote:
Hi Dwight.
I agree with you that the green RX marker doesn't stand out ... but I'm
curious as to why that's a probl
Hi Dwight.
I agree with you that the green RX marker doesn't stand out ... but I'm
curious as to why that's a problem for you, if you are talking about FT8 on
HF anyway (you didn't mention how you are using WSJT-X).
The software simultaneously decodes all the signals it can across the whole
wat
Hi All,
I would object to such a change.
I have a low opinion of always on top windows, especially big ones. Also
it is not possible to implement this when there are multiple instances
running.
TBH I would rather the component windows of WSJT-X be dock widgets that
can be floated if require
Bill Somerville writes:
>
> CQ DX NO3M
> is the correct form and is a standard message form, you can add your
> locator as well just like a normal CQ call.
Thanks for that Bill, that will do the trick.
73 de Guy G4DWV/4X1LT
Bill Somerville writes:
>
> On 06/03/2015 11:15, John Nelson wrote:
> > Hi Bill,
> Hi John,
Hi Bill and John -
> >
> > I have noticed a similar problem raised by Paul.As Paul points out
the "DX" is used by the dictionary as a
> DXCC entry.
> >
> > CQ DX !Phillipines
> >
> > In m
On 06/03/2015 11:15, John Nelson wrote:
> Hi Bill,
Hi John,
>
> I have noticed a similar problem raised by Paul.As Paul points out the
> "DX" is used by the dictionary as a DXCC entry.
>
> CQ DX !Phillipines
>
> In my case, double-clicking on does not generate a standard messa
Hi Bill,
I have noticed a similar problem raised by Paul.As Paul points out the "DX"
is used by the dictionary as a DXCC entry.
CQ DX !Phillipines
In my case, double-clicking on does not generate a standard message at
all. This is not the same result as seen by Paul who
On 06/03/2015 07:05, Paul DU2/WA8UGN wrote:
> Bill Somerville writes:
>
>>
> Hi Bill and all -
Hi Paul,
>
>> On 06/03/2015 00:09, Eric NO3M wrote:
>>Hi Eric,
>>
>>
>>
>>I ran into a similar situation with the following message:
>>CQ NO3M DX
>>
>>
Bill Somerville writes:
>
>
Hi Bill and all -
> On 06/03/2015 00:09, Eric NO3M wrote:
> Hi Eric,
>
>
>
> I ran into a similar situation with the following message:
> CQ NO3M DX
>
> CQ DX NO3M
> is the correct form and is a standard message form, you
On 6/03/2015 11:09 AM, Eric NO3M wrote:
> perhaps something JT-Alert does for them? Of course, JT-Alert is not
> able to run on *nix, so that's not an option here.
No. JTAlert doesn't play with the TX settings of WSJT-X.
de Laurie VK3AMA
---
Excellent... will try it later when 160 wakes up. Thanks for the info!
73 Eric NO3M
On 03/05/2015 07:30 PM, Bill Somerville wrote:
On 06/03/2015 00:09, Eric NO3M wrote:
Hi Eric,
I ran into a similar situation with the following message:
CQ NO3M DX
CQ DX NO3M
is the correct form and is a s
On 06/03/2015 00:09, Eric NO3M wrote:
Hi Eric,
I ran into a similar situation with the following message:
CQ NO3M DX
CQ DX NO3M
is the correct form and is a standard message form, you can add your
locator as well just like a normal CQ call.
Note that this only works with "CQ" "CQ DX" "QRZ"
I ran into a similar situation with the following message:
CQ NO3M DX
to keep stateside callers from answering. I had assumed the "CQ" would
have been picked up and TX Enable persist after each invocation.
However, that was not the case. I saw other DX stations at the time
using the same f
On 05/03/2015 22:07, Guy G4DWV/4X1LT wrote:
Hi Guy,
> Michael Black writes:
>
>>
>> Sounds like you have "Disable TX after sending 73" checked in
> File/Settings/General.
>
> I do, but standard CQ calls go out okay indefinitely and custom ones do not.
> The Disable after 73 setting is the same in
Michael Black writes:
>
>
> Sounds like you have "Disable TX after sending 73" checked in
File/Settings/General.
I do, but standard CQ calls go out okay indefinitely and custom ones do not.
The Disable after 73 setting is the same in both cases. The expected
behaviour is that both types of CQ
Sounds like you have "Disable TX after sending 73" checked in
File/Settings/General.
Mike W9MDB
From: Guy [mailto:g...@drteeth.co.uk]
Sent: Thursday, March 05, 2015 3:05 PM
To: wsjt-devel@lists.sourceforge.net
Subject: [wsjt-devel] Enhancement request
I am not a programmer at all, b
29 matches
Mail list logo
