Re: [wsjt-devel] USB protocolo

[José Aparecido Pereira]

Eu não acho que é isso
Eu recebi este decimal decimal por UDP / ip e quando eu traduzo para
ascii desta maneira
Além de muitas outras informações provenientes de UDP / ip, ainda não
consigo codificar comletamente.

exe:
'0001 0006 878374844588 0 107 240 208 0003 7084560006 908053668675 0003
454953 0003 708456 05 241 005 241 0006 808953746580 0006 71715153116119
0004 71714952 0 255 255 255 255 0
  '? Para WSJT - X k Ð Ð? FT 8? ZP 5 BVK? - 1 5? FT 8? para para PY 5 JAP? GG
3 5 tw? GG 1 4 ÿ ÿ ÿ ÿ

alguém pode informar o protocolo completo?

0001000687837484458801072402080003708456000667695077867156000370845600100913400913400068089537465867171515311611900047070525502552552552550
var-> 151
­¼ËÚWSJT-X kðÐFT8CE2MVF8FT8†  †
PY5JAPGG35twFF47    str-> 33
000200068783748445881425419572000463185153153160021720001126001767813268883280895065768232717154540
var-> 103
­¼ËÚWSJT-X þÃH?¹™™  ¬~CQ DX PY2ALR GG66   str->
29
00020006878374844588142541957263185153153160032540001126001467813280845071847332717254520
var-> 97
­¼ËÚWSJT-X þÃH?¹™™  þ~CQ PT2GTI GH64   str-> 26
000200068783748445881425419572255255255232631851531531600515700011260013678132878650788932707848500
var-> 103
­¼ËÚWSJT-X þÃHÿÿÿè?¹™™  ~
CQ WV2NY FN02   str-> 25
0002000687837484458814254195722552552552346320115315316006108000112600157553766732757056779032824348490
var-> 107
­¼ËÚWSJT-X þÃHÿÿÿê?É™™  l~K5LC KF8MZ R+01   str-> 27
000200068783748445881425419572255255255240631851531531600721900011260013875782807732878852673255510
var-> 103
­¼ËÚWSJT-X þÃHÿÿÿð?¹™™  Û~
W9RPM WX4C 73   str-> 25
00020006878374844588142541957225525525524763230102102960845000112600156876537765843287498575324549530
var-> 105
­¼ËÚWSJT-X þÃHÿÿÿ÷?æff`  -~DL5MAT W1UK -15   str->
28
00020006878374844588142541957225525525524663211515164091511260016866949748332806548728766324549540
var-> 106
­¼ËÚWSJT-X þÃHÿÿÿö?Ó33@  –~VE1JS PA0HWB -16   str->
30
000100068783748445880107240208000370845600066769507786715600037084560913400913400068089537465867171515311611900047070525502552552552550
Onde-> 151
­¼ËÚWSJT-X kðÐFT8CE2MVF8FT8  †  †
PY5JAPGG35twFF47    str-> 33
00068783748445880003000949465646484511455114485457 var-> 58
­¼ËÚWSJT-X1.8.0-rc2r8069  str-> 18
0001000687837484458801072402080003708456000667695077867156000370845600100913400913400068089537465867171515311611900047070525502552552552550
aviso> 151
­¼ËÚWSJT-X kðÐFT8CE2MVF8FT8†  †
PY5JAPGG35twFF47    str-> 33
000200068783748445881425425322425525525523563201153153160012230001126001757724965693274825178906732807755520
aviso> 112
­¼ËÚWSJT-X þýàÿÿÿë?É™™  ß~9H1AE JR3NZC PM74   str->
28
000200068783748445881425425322425525525524163185153153160031040001126001478578469833287855077328282820
aviso> 106
¼ËÚ? ? ? WSJT-X ?? þýàÿÿÿñ? ¹ ™pecial? H? ~? N9TES WU2M RRR str-> 25
0002000687837484458814425425322400010043400011260016757056779032808952698032717155560
var-> 92
­¼ËÚWSJT-X þýà  "~KF8MZ PY4EP GG78   str->
24
000200068783748445881414254253224255255255247632411531531600414112600186765497669873267655177827832707052540
var-> 114
¼ËÚ? ? ? WSJT-X ?? þýàÿÿÿ ÷? Ñ ™ ™? Œ? ~? CA1LEW CA3MRN FF46 str-> 29
0002000687837484458814142542532242552552552376318515315316005171126001775705677903280825582666532727348510
var-> 112
¼ËÚ? ? ? WSJT-X ?? þýàÿÿÿí? ¹ ™pecial? ª? ~? KF8MZ PR7RBA HI03 str-> 28
0002000687837484458814254252532240008631851531531600523300011260013678132808053709032717152500
var-> 96
¼ËÚ? Para WSJT-X þ þ ™ 
CQ PP5FZ GG42 str-> 24
0002000687837484458814254253224242552552552481912275151640761126001467813267885365667732717049530
var-> 103
­¼ËÚWSJT-X þýàÿÿÿø¿ã33@  <~CQ CX5ABM GF15   str-> 24
00020006878374844588141425425322425525525523412807970001126001467813286855077836532777456570
var-> 98
­¼ËÚWSJT-X þýàÿÿÿê€  a~CQ VU2MSA MJ89   str-> 22


Livre
de vírus. www.avast.com
.
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

2018-02-20 1:01 GMT-03:00 John Nogatch :

> On Sat, Feb 17, 2018 at 10:36 AM, José Aparecido Pereira
>  wrote:
> ...
> > ... the information received by the UDP / ip protocol port WSJT-x
> > could someone please forward this information to me?
>
> The format of the UDP messages is documented here:
> https://sourceforge.net/p/wsjt/wsjt/HEAD/tree/branches/
> wsjtx/NetworkMe

Re: [wsjt-devel] WSJT-X v1.9.0-rc2: Testing of FT8 DXpedition Mode

[jarmo]

Mon, 26 Feb 2018 13:55:44 -0500
Joe Taylor  kirjoitti:

> 8. Improved waterfall sensitivity for very weak signals

For me happened opposite, waterfall became more blurry, have
to try adjust, but can't get it so sharp as in version 1.8.0.
And very weak signals are more invisible?

Couple of other friends noticed same. 1 win version, 2 linux versions.

Jarmo, oh1mrr 

--
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] Memory Leak in jt9 Process

[Doug Collinge]

There seems to be a memory leak in the jt9 process started by wsjtx. I have
included a chart showing the memory use growing from about 20MiB to over
300MiB in the course of 11 hours. I set wsjtx to monitor 40m overnight and
recorded the memory stats produced by /proc/*/statm at one minute
intervals. The change in slope of the curves indicates the band opening and
more signals being decoded.

The configuration here is Ubuntu 17.10 with an RTL-SDR. gqrx demodulates
USB, filters and feeds the audio to wsjt-x 1.9.0-rc1 using pulseaudio.

Doug VE7GNU


​
--
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] 1.9 RC2 - UI Suggestion

[Joe Taylor]

Hi Phil,

On 2/26/2018 5:44 PM, Phil Frost wrote:
The lack of contributors to the UI should not be surprising. With such 
dismissiveness and opposition to change, who's going take the time to 
implement a patch only to endure belittlement and rejection?



I don't think anyone here has been dismissive or opposed to change. 
Quite the contrary.  As Bill wrote: the project is open source, anyone 
can submit patches, and many patches get accepted.


Do keep in mind that we try to maintain platform independence.  Making a 
GUI look good (and behave intuitively) on one platform is not always 
good enough.  Making it good for one mode, say FT8, may not be good enough.


Simply asking for somebody else to "do something about it", whatever 
"it" may be, will usually be assigned a much lower priority than 
evaluating a proffered solution to a perceived problem.


-- Joe, K1JT

--
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] Feature Request: TCP CAT for Elecraft K3

[Lee J. Imber (WW2DX)]

Hello Team,

First off, I hope this is the correct place to request features, if not,
please point me to the appropriate location.

I also wanted to thank the dev team for really providing a awesome addition
to the hobby! Great work! I am planning on using the new FT8 DXP mode in
upcoming visits to V2 and CY9.

I am looking for a feature to be able to point WSJT-X’s RADIO settings to
connect to a TCP server for a Elecraft K3 (like the Hamlib option)  but
instead of a serial port I want to point to a TCP IP address and port.

For example:

https://www.dropbox.com/s/yz6atskl1go1mnq/Screenshot%202018-02-26%2015.26.59.png?dl=0

(I tried to include the image but my email was kicked back from source
forge)

If this is possible, I would like to request the ability to be able to
disable the polling when this option is selected.

The control lines would not be supported, just the data.

This feature is requested for remote operation.

Thanks for your time,

73 Lee
WW2DX
--
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] 1.9 RC2 - UI Suggestion

[Bill Somerville]

On 26/02/2018 22:44, Phil Frost wrote:
In this thread you have a well-illustrated, constructive, and specific 
suggestion from a user about a particular aspect of the UI which is 
confusing, surprising, or less helpful than it could be. Your response 
of "I don't see a problem", "The principle of least surprise is 
working as intended here", and "should be familiar to anyone who has 
used a mouse + windows application for computer interaction" indicates 
you see no issue with the UI, and anyone who thinks otherwise is a fool.


The lack of contributors to the UI should not be surprising. With such 
dismissiveness and opposition to change, who's going take the time to 
implement a patch only to endure belittlement and rejection?


Phil,

this thread started with Gary, ZL2IFB, commenting that when he selected 
or placed the cursor on a piece of text he was surprised that when he 
typed a numeric field nearby did not change. He suggested a UI change 
that is unnecessary since selecting the text to be changed already 
achieves his goal. I am not calling anyone a fool, just pointing out 
that his expectation was as unlikely to be met as a by word processing 
application that changed text elsewhere when selecting a piece of text 
and typing.


With respect to those who would suggest or sometimes demand changes, I 
suspect Joe is expressing the view that talk is easy but few do the 
walking necessary to contribute. The project is open source, anyone can 
contribute patches and many get accepted.


73
Bill
G4WJS.


--
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] 1.9 RC2 - UI Suggestion

[Phil Frost]

In another thread today with a UI suggestion, Joe Taylor emphasized the
small number of contributors to WSJT-X, as well as how the limited time
available to those contributors means UI polish tends to take a back seat
to functionality. The post concluded by welcoming UI improvements from the
community, but notably without conceding the suggestion may be a good one.

In this thread you have a well-illustrated, constructive, and specific
suggestion from a user about a particular aspect of the UI which is
confusing, surprising, or less helpful than it could be. Your response of
"I don't see a problem", "The principle of least surprise is working as
intended here", and "should be familiar to anyone who has used a mouse +
windows application for computer interaction" indicates you see no issue
with the UI, and anyone who thinks otherwise is a fool.

The lack of contributors to the UI should not be surprising. With such
dismissiveness and opposition to change, who's going take the time to
implement a patch only to endure belittlement and rejection?

On Mon, Feb 26, 2018 at 10:16 PM Bill Somerville 
wrote:

> Hi Phil,
>
> comments in line below.
>
>
> On 26/02/2018 21:47, Phil Frost wrote:
>
> On Mon, Feb 26, 2018 at 9:12 PM Bill Somerville 
> wrote:
>
>> BTW this is not our design but standard Qt widget behaviour, which is
>> consistent with recognized "standard" GUI design principles.
>>
>
> While the double- and triple-click semantics are typical, I'd call
> including the unit ("Hz") and labels ("Rx" or "Tx") within the box are not.
>
> I don't see a problem, doing so saves some valuable space because no
> separate label is required.
>
>
> See Microsoft's guidelines:
> https://msdn.microsoft.com/en-us/library/windows/desktop/bb226829(v=vs.85).aspx
>
> "You may specify units (seconds, connections, and so on) in parentheses
> after the label. Place units in parentheses after the label and before the
> colon."
>
> Adding units after the numbers they apply to is standard in written text,
> why not in UIs too?
>
>
> Or GNOME: https://developer.gnome.org/hig/stable/spin-boxes.html.en
>
> "Label the spin box with a text label above it or to its left, using
> sentence capitalization. Provide an access key in the label that allows the
> user to give focus directly to the spin box."
>
> GNOME's example does include units in the box, but I'd expect when they
> are in the box I could edit them. So I should be able to enter "1200" or
> "1.2 kHz" or even "1.2e-06 GHz", but this does not appear to be the case.
>
> One of the issues with GNOME and other single system frameworks is that
> hot-keys become very scarce and it becomes almost impossible to design a
> multi-platform UI with a rich set of such hot-keys. That does mean that Qt
> applications do become rather mouse centric but there is little we can do
> if the desktop manager uses up most of the available accelerator key
> strokes (ALT+ CTRL+ CMD+ META+ etc.) before we get a look in.
>
>
> I don't think Apple even has spinboxes.
>
> Of course they do, here is an example - with text included in the entry
> field:
>
>
> https://developer.apple.com/macos/human-interface-guidelines/windows-and-views/boxes/
>
>
>
> Regardless of QT's default behavior or any of these guidelines, any UI
> that requires explanation for something as simple as entering a number is
> not quite right.
>
> I don't see a problem, spin boxes contain numeric text (or something akin
> to numeric text like a letter selection A, B, C, ...) that have a forward
> and backward sequence defined, may or may not support wrap around, can be
> directly entered just like any text field and have useful, relevant, mouse
> and keyboard semantics like sub-controls to click up and down, keyboard
> arrow up/down, and keyboard page up/down for larger increments.
>
> We are discussing this because someone selected some text and expected
> something else to be replaced when they typed, the bad behaviour would have
> been if what they wanted actually happened. The principle of least surprise
> is working as intended here.
>
> These sort of widgets occur in most applications and should be familiar to
> anyone who has used a mouse + windows application for computer interaction.
>
> 73
> Bill
> G4WJS.
>
> --
> 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
>
--
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/wsj

Re: [wsjt-devel] 1.9 RC2 - UI Suggestion

[Bill Somerville]

Hi Phil,

comments in line below.

On 26/02/2018 21:47, Phil Frost wrote:
On Mon, Feb 26, 2018 at 9:12 PM Bill Somerville > wrote:


BTW this is not our design but standard Qt widget behaviour, which
is consistent with recognized "standard" GUI design principles.


While the double- and triple-click semantics are typical, I'd call 
including the unit ("Hz") and labels ("Rx" or "Tx") within the box are 
not.
I don't see a problem, doing so saves some valuable space because no 
separate label is required.


See Microsoft's guidelines: 
https://msdn.microsoft.com/en-us/library/windows/desktop/bb226829(v=vs.85).aspx 
 



"You may specify units (seconds, connections, and so on) in 
parentheses after the label. Place units in parentheses after the 
label and before the colon."
Adding units after the numbers they apply to is standard in written 
text, why not in UIs too?


Or GNOME: https://developer.gnome.org/hig/stable/spin-boxes.html.en

"Label the spin box with a text label above it or to its left, using 
sentence capitalization. Provide an access key in the label that 
allows the user to give focus directly to the spin box."


GNOME's example does include units in the box, but I'd expect when 
they are in the box I could edit them. So I should be able to enter 
"1200" or "1.2 kHz" or even "1.2e-06 GHz", but this does not appear to 
be the case.
One of the issues with GNOME and other single system frameworks is that 
hot-keys become very scarce and it becomes almost impossible to design a 
multi-platform UI with a rich set of such hot-keys. That does mean that 
Qt applications do become rather mouse centric but there is little we 
can do if the desktop manager uses up most of the available accelerator 
key strokes (ALT+ CTRL+ CMD+ META+ etc.) before we get a look in.


I don't think Apple even has spinboxes.
Of course they do, here is an example - with text included in the entry 
field:


https://developer.apple.com/macos/human-interface-guidelines/windows-and-views/boxes/



Regardless of QT's default behavior or any of these guidelines, any UI 
that requires explanation for something as simple as entering a number 
is not quite right.


I don't see a problem, spin boxes contain numeric text (or something 
akin to numeric text like a letter selection A, B, C, ...) that have a 
forward and backward sequence defined, may or may not support wrap 
around, can be directly entered just like any text field and have 
useful, relevant, mouse and keyboard semantics like sub-controls to 
click up and down, keyboard arrow up/down, and keyboard page up/down for 
larger increments.


We are discussing this because someone selected some text and expected 
something else to be replaced when they typed, the bad behaviour would 
have been if what they wanted actually happened. The principle of least 
surprise is working as intended here.


These sort of widgets occur in most applications and should be familiar 
to anyone who has used a mouse + windows application for computer 
interaction.


73
Bill
G4WJS.

--
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] wsjtx_status.patch

[Michael Black]

 Add hisGrid to wsjtx_status.txt so programs like PstRotatorAZ can use
actual grid. Assigns "NA" if not available.

https://www.dropbox.com/s/rbibasioq6io8nd/status.patch?dl=1


de Mike W9MDB
--
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] 1.9 RC2 - UI Suggestion

[Phil Frost]

On Mon, Feb 26, 2018 at 9:12 PM Bill Somerville 
wrote:

> BTW this is not our design but standard Qt widget behaviour, which is
> consistent with recognized "standard" GUI design principles.
>

While the double- and triple-click semantics are typical, I'd call
including the unit ("Hz") and labels ("Rx" or "Tx") within the box are not.

See Microsoft's guidelines:
https://msdn.microsoft.com/en-us/library/windows/desktop/bb226829(v=vs.85).aspx

"You may specify units (seconds, connections, and so on) in parentheses
after the label. Place units in parentheses after the label and before the
colon."

Or GNOME: https://developer.gnome.org/hig/stable/spin-boxes.html.en

"Label the spin box with a text label above it or to its left, using
sentence capitalization. Provide an access key in the label that allows the
user to give focus directly to the spin box."

GNOME's example does include units in the box, but I'd expect when they are
in the box I could edit them. So I should be able to enter "1200" or "1.2
kHz" or even "1.2e-06 GHz", but this does not appear to be the case.

I don't think Apple even has spinboxes.

Regardless of QT's default behavior or any of these guidelines, any UI that
requires explanation for something as simple as entering a number is not
quite right.
--
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] 1.9 RC2 - UI Suggestion

[Bill Somerville]

On 26/02/2018 20:22, g...@isect.com wrote:


This is what happens when I double-click the “Tx” area …

If I then start typing a number, the blue selection is cleared and my 
numbers are ignored.  [On my system anyway.]



Hi Gary,

what you describe is not quite the full story. If you click anywhere to 
the left of the numeric field, which includes double-clicking the 
leading non-numeric prefix text then digits you type will be prepended 
to the existing numeric field -- assuming the result is valid. The same 
applies to any position to the right of the numeric field except that 
new digits are appended to the numeric field -- assuming the result is 
valid.


If you want to replace the value then it must be selected first, you can 
do that quickly and easily by triple-clicking anywhere in the spin box 
or double-clicking the numeric part of the field; then type in a new 
value. BTW this is not our design but standard Qt widget behaviour, 
which is consistent with recognized "standard" GUI design principles.


73
Bill
G4WJS.
--
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] 1.9 RC2 - UI Suggestion

[George J Molnar]

Thanks for the clarification, Joe.

George J Molnar, CEM, CHPP
@GJMolnar | KF2T | AFA9GM

> On Feb 26, 2018, at 3:47 PM, Joe Taylor  wrote:
> 
>> On 2/26/2018 3:20 PM, George J Molnar wrote:
>> Any chance for 6-place grid squares at VHF & higher?
> 
> Of course you can send a 6-character locator as part of a free text message.
> 
> But as a JT-style structured message??
> 
> Think about it this way: A 4-character Maidenhead locator fits in a 15-bit 
> field.  A 6-character locator must allow for AA to RR as the final two 
> characters.  That's another 18 x 18 = 324 possibilities, or another 9 bits.  
> All 72 bits in the JT structured messages are "spoken for".  We don't have 9 
> unassigned and available bits.
> 
>-- Joe, K1JT
> 
> --
> 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


--
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] 1.9 RC2 - UI Suggestion

[Joe Taylor]

On 2/26/2018 3:20 PM, George J Molnar wrote:

Any chance for 6-place grid squares at VHF & higher?


Of course you can send a 6-character locator as part of a free text 
message.


But as a JT-style structured message??

Think about it this way: A 4-character Maidenhead locator fits in a 
15-bit field.  A 6-character locator must allow for AA to RR as the 
final two characters.  That's another 18 x 18 = 324 possibilities, or 
another 9 bits.  All 72 bits in the JT structured messages are "spoken 
for".  We don't have 9 unassigned and available bits.


-- Joe, K1JT

--
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] WSJT-X v1.9.0-rc2: another small UI enhancement suggestion

[gary]

PS  Would it be possible to retain rather than erase the waterfall image (the 
blobs) when we toggle the Controls, please?  I realize showing the controls 
takes some space from the window so it’s no problem if removing the controls 
leaves a blank area at the bottom where the controls used to be, but could the 
blobs above remain on show?

 

 

From: g...@isect.com [mailto:g...@isect.com] 
Sent: Tuesday, 27 February 2018 9:08 a.m.
To: 'WSJT software development' 
Subject: [wsjt-devel] WSJT-X v1.9.0-rc2: another small UI enhancement suggestion

 

One more UI suggestion: when we’re trying to identify blobs on the waterfall, 
it’s not easy to figure out (at a glance) the exact audio frequencies since 
most of the scale markers are unlabelled.  I’d suggest changing from this …

 



 

… to something more like this …

 



 

I’ve deliberately chosen a smaller font size in light grey so the intermediate 
values are less prominent than the round 500’s.

 

73

Gary  ZL2iFB

--
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] WSJT-X v1.9.0-rc2: another small UI enhancement suggestion

[Joe Taylor]

Hi Gary,

GUI design is trivial when you're dealing with a static mock-up that 
doesn't actually do anything.  Implementing a functional and attractive 
user interface is far from trivial, especially in a program like WSJT-X 
that operates in many different "modes" with very different goals.


Active contributors to WSJT-X comprise a tiny group of people -- 
individuals with many other demands on their time.  It should be fairly 
obvious that our top priorities lie much more often in areas of program 
capability and functionality rather than creating a "pretty face". 
Typically we work first on new capabilities, leaving GUI design issues 
until "some later time".


On the other hand, we like pretty faces, too!  We're always on the 
lookout for potential contributors with skills and interests in GUI 
design.

-- 73, Joe, K1JT

On 2/26/2018 3:07 PM, g...@isect.com wrote:
One more UI suggestion: when we’re trying to identify blobs on the 
waterfall, it’s not easy to figure out (at a glance) the exact audio 
frequencies since most of the scale markers are unlabelled.  I’d suggest 
changing from this …


… to something more like this …

I’ve deliberately chosen a smaller font size in light grey so the 
intermediate values are less prominent than the round 500’s.


73

Gary  ZL2iFB


--
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] 1.9 RC2 - UI Suggestion

[gary]

Hi Bill.

 

This is what happens when I double-click the “Tx” area …

 



 

If I then start typing a number, the blue selection is cleared and my numbers 
are ignored.  [On my system anyway.]

 

[And yes that’s another truncated pop-up message 😊]

 

73

Gary  ZL2iFB

 

From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Tuesday, 27 February 2018 9:01 a.m.
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] 1.9 RC2 - UI Suggestion

 

On 26/02/2018 19:46, g...@isect.com   wrote:

In the same vein, the Tx and Rx frequency setting boxes contain 
boilerplate/static text "Tx" or "Rx" and "Hz".  If the static text was moved 
outside the data-entry box, we could click anywhere in the box and start typing 
a new value (e.g. on the numeric keypad), rather than having to double-click 
specifically on the value part.  It’s a small point, but it will help make it 
just a bit easier when we’re in a hurry to catch the DX on FT8!

 

Same deal with the report box: “Report” should be outside the data-entry box, I 
think.

Hi OM (Gary?),

you should be able to double-click anywhere in the spin boxes and type any 
valid value (same applies to using the up/down arrows or page up/down to move 
in regular intervals), there is no need to click specifically on the numeric 
part.

73
Bill
G4WJS.

--
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] 1.9 RC2 - UI Suggestion

[gary]

Aha!

Sorry our messages crossed-over Bill.

73
Gary  ZL2iFB

-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Tuesday, 27 February 2018 9:03 a.m.
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] 1.9 RC2 - UI Suggestion

On 25/02/2018 20:05, Tom Melvin wrote:
> Hi All
>
> Just a little observation on the new 1.9 rc2  (Windows OS) - Very minor
but if anyone in the area.
>
> The 'Hold Tx Freq' seems to sit on it's own - I have limited screen real
estate so it sticks out.
>
> If the 'Hold Tx Freq' was dropped in line with 'Report Box' it would allow
the bottom box to be slightly reduced - just 'looks' a little odd at
present.
>
> Thanks
>
> Tom
> GM8MJV

Hi Tom,

agreed it does look a bit clunky when you can't see the hidden widgets that
occupy the space to the left. They are present in other modes. The gap is a
consequence of the grid layout manager we use to line up the widgets in a
regular grid in that area of the UI.

73
Bill
G4WJS.



--
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


--
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] 1.9 RC2 - UI Suggestion

[George J Molnar]

Also suggest “NA VHF Contest” label be changed to simply “Grids."

Any chance for 6-place grid squares at VHF & higher?




George J Molnar
Washington, DC, USA
KF2T   -   @GJMolnar









--
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] 1.9 RC2 - UI Suggestion

[George J Molnar]

Like ZL2IFB’s “arrowheads” idea. Yes, the existing model makes sense, but his 
idea makes (in my opinion) more sense.

Great work on rc2, guys!


 
George J Molnar
Washington, DC, USA
KF2T   -   @GJMolnar






> 

--
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] WSJT-X v1.9.0-rc2: another small UI enhancement suggestion

[gary]

One more UI suggestion: when we’re trying to identify blobs on the waterfall, 
it’s not easy to figure out (at a glance) the exact audio frequencies since 
most of the scale markers are unlabelled.  I’d suggest changing from this …

 



 

… to something more like this …

 



 

I’ve deliberately chosen a smaller font size in light grey so the intermediate 
values are less prominent than the round 500’s.

 

73

Gary  ZL2iFB

--
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] Band change patch

[Michael Black]

 This patch was submitted Nov 2 but never applied.
It comes from the bug identified in this thread where changing the rig freq
does not adjust to the remembered power levels.

https://sourceforge.net/p/wsjt/mailman/message/36101238/


Index: mainwindow.cpp
===
--- mainwindow.cpp  (revision 8534)
+++ mainwindow.cpp  (working copy)
@@ -1925,6 +1925,7 @@
   ui->bandComboBox->setCurrentText (band_name);
   m_wideGraph->setRxBand (band_name);
   m_lastBand = band_name;
+  band_changed(dial_frequency);
 }

   // search working frequencies for one we are within 10kHz of (1 Mhz

de Mike W9MDB
--
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] 1.9 RC2 - UI Suggestion

[Bill Somerville]

On 26/02/2018 19:46, g...@isect.com wrote:


In the same vein, the Tx and Rx frequency setting boxes contain 
boilerplate/static text "Tx" or "Rx" and "Hz".  If the static text was 
moved /outside/ the data-entry box, we could click anywhere in the box 
and start typing a new value (e.g. on the numeric keypad), rather than 
having to double-click specifically on the value part.  It’s a small 
point, but it will help make it just a bit easier when we’re in a 
hurry to catch the DX on FT8!


Same deal with the report box: “Report” should be /outside/ the 
data-entry box, I think.



Hi OM (Gary?),

you should be able to double-click anywhere in the spin boxes and type 
any valid value (same applies to using the up/down arrows or page 
up/down to move in regular intervals), there is no need to click 
specifically on the numeric part.


73
Bill
G4WJS.

--
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] 1.9 RC2 - UI Suggestion

[Bill Somerville]

On 25/02/2018 20:05, Tom Melvin wrote:

Hi All

Just a little observation on the new 1.9 rc2  (Windows OS) - Very minor but if 
anyone in the area.

The ‘Hold Tx Freq’ seems to sit on it’s own - I have limited screen real estate 
so it sticks out.

If the ‘Hold Tx Freq’ was dropped in line with ‘Report Box’ it would allow the 
bottom box to be slightly reduced - just ‘looks’ a little odd at present.

Thanks

Tom
GM8MJV


Hi Tom,

agreed it does look a bit clunky when you can't see the hidden widgets 
that occupy the space to the left. They are present in other modes. The 
gap is a consequence of the grid layout manager we use to line up the 
widgets in a regular grid in that area of the UI.


73
Bill
G4WJS.


--
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] 1.9 RC2 - UI Suggestion

[gary]

In the same vein, the Tx and Rx frequency setting boxes contain
boilerplate/static text "Tx" or "Rx" and "Hz".  If the static text was moved
outside the data-entry box, we could click anywhere in the box and start
typing a new value (e.g. on the numeric keypad), rather than having to
double-click specifically on the value part.  It's a small point, but it
will help make it just a bit easier when we're in a hurry to catch the DX on
FT8!

 

Same deal with the report box: "Report" should be outside the data-entry
box, I think.

 

I'm suggesting a change from this (in v1.9.0 RC2):

 



 

to something more like this:

 



 

I've suggested added a little color cue to the frequencies, and changing the
tiny backward-facing arrows to bold forward-facing arrowheads, something I
suggested before to reflect the idea of 'Move the Tx channel marker to the
Rx channel' for the top one.  It seems more intuitive to me.  I wonder what
others think?

 

"Freq" in "Hold Tx Freq"is superfluous, so we can save a little screen
real-estate by omitting the text and re-aligning things.

 

Reducing the vertical height of the controls area on the main screen still
further (without things getting too cramped) would leave more space for
decodes.   In fact, I wonder if it would be feasible to move all the
controls to the left or right of the existing Band Activity and Rx Frequency
panes, making the window letterbox shaped rather than square?  I guess that
may not work for users with narrow screens, though, so a user option would
be nice.

 

These are just my suggestions, based on heavy use for HF FT8 on a Windows
system (4,000 QSOs and counting!).

 

73

Gary  ZL2iFB

 

-Original Message-
From: Tom Melvin [mailto:t...@tkrh.co.uk] 
Sent: Monday, 26 February 2018 9:06 a.m.
To: WSJT software development 
Subject: [wsjt-devel] 1.9 RC2 - UI Suggestion

 

Hi All

 

Just a little observation on the new 1.9 rc2  (Windows OS) - Very minor but
if anyone in the area.

 

The 'Hold Tx Freq' seems to sit on it's own - I have limited screen real
estate so it sticks out.

 

If the 'Hold Tx Freq' was dropped in line with 'Report Box' it would allow
the bottom box to be slightly reduced - just 'looks' a little odd at
present.

 

Thanks

 

Tom

GM8MJV

 

 

 

 


--

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

--
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] WSJT-X v1.9.0-rc2: Testing of FT8 DXpedition Mode

[Joe Taylor]

The WSJT Development Group is pleased to announce a Release Candidate of 
WSJT-X Version 1.9.0.  This is a second beta release, so it's called 
v1.9.0-rc2. A first candidate release, v1.9.0-rc1, has already been 
tested in the field by a small test group.  A General Availability (GA) 
release of v1.9.0 will be announced at a suitable time in the near 
future.  After that time you should no longer use any -rc# candidate.


Here’s a short list of features and capabilities added to WSJT-X since 
Version 1.8.0:


1. New FT8 DXpedition Mode to facilitate high QSO rates in pileup situations

2. Decoding improvements for JT65 mode, including a priori (AP) decoding 
when VHF/UHF/Microwave features are enabled


3. Optional Auto-Sequencing in JT4, JT9, and JT65 when VHF/UHF/Microwave 
features are enabled


4. Better suppression of low-confidence false decodes generated by AP 
decoding in FT8 mode


5. Improved decoding performance for WSPR mode, especially effective at 
LF and MF


6. Minor adjustments to auto-sequencing behavior

7. More flexible Doppler control features for EME

8. Improved waterfall sensitivity for very weak signals

9. Automatic real-time forwarding of logged information to N1MM Logger+

10. Expanded and improved UDP messages sent to companion programs

11. Bug fixes and other minor tweaks to user interface


*Public Test of FT8 DXpedition Mode*


A primary purpose of this beta release is to allow field testing of FT8 
DXpedition Mode.  If you decide to install v1.9.0-rc2, please help us by 
participating in a public test run scheduled for March 6-7 (evening of 
March 6, NA time).  The goal is to simulate a rare-DXpedition pileup by 
having many stations ("Hounds") calling and trying to work a designated 
pseudo-DXpedition station ("Fox").  Note that everyone participating in 
the test *MUST* use WSJT-X v1.9.0-rc2.  In addition, you must read and 
carefully follow the instructions posted here:

http://physics.princeton.edu/pulsar/k1jt/FT8_DXpedition_Mode.pdf

Reading the instructions for *FT8 DXpedition Mode* is very important!

If you have legitimate access to more than one callsign (XYL, club call, 
or whatever) please feel free to call and work the Fox more than once. 
We want the test pileup to be as deep as possible.


The scheduled test will take place as follows:

DateUTC   Frequency
-
Mar 6  2300   14.080 MHz
Mar 7     10.141
Mar 7  01007.080
Mar 7  02003.585

The indicated USB dial frequencies are subject to change, depending on 
other band usage at the time.  If last-minute instructions are necessary 
they will be posted here:

http://physics.princeton.edu/pulsar/k1jt/DXpedition_Mode_Test.txt

Note that the dial frequencies are NOT the conventional FT8 operating 
frequencies for each band.  DXpedition Mode should *NOT* be used on 
standard FT8 operating frequencies.


Of course you may also choose to do your own testing of FT8 DXpedition 
Mode together with a group of colleagues.  One station would act as Fox, 
the others as Hounds.  In such tests the Fox will be limited to using a 
single Tx "slot".



Installation packages for Windows, Linux, Macintosh, and Raspian Jessie 
have been posted on the WSJT web site here:

http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
Scroll down to the bottom of the page to find a link to the installation 
package for your system.


You can also download the packages from our SourceForge site:
https://sourceforge.net/projects/wsjt/files/

Please report any problems to email list 
wsjt-devel@lists.sourceforge.net.  You must be a subscriber in order to 
post there.


-- 73 from Joe, K1JT, for the WSJT Development Group

--
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] 1.9 RC2 - UI Suggestion

[Tom Melvin]

Hi All

Just a little observation on the new 1.9 rc2  (Windows OS) - Very minor but if 
anyone in the area.

The ‘Hold Tx Freq’ seems to sit on it’s own - I have limited screen real estate 
so it sticks out.

If the ‘Hold Tx Freq’ was dropped in line with ‘Report Box’ it would allow the 
bottom box to be slightly reduced - just ‘looks’ a little odd at present.

Thanks

Tom
GM8MJV




--
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