Hello Laurie and the group,

I'm just wondering if it is possible to be able to clear the "Calls you spotted" and/or the "Your call spotted" listings?
There are times, such as when I have not been active for a while, that it would be nice to clear these listings and see only current listings in the columns.

Just an idea....

73 de Phil GU0SUP

Laurie,
Looks like your development will always be in revision mode with all these new decodes..

This is a repost as requested by JT
Joe Taylor asked for a cross post. I've been testing ver 1.1 for about a week. Its ability to monitor both JT65 and JT9 simultaneously, and to jump between modes with nothing but a mouse click, is very powerful. If you never tried JT9 here's a great way to compare it with JT65. If you're already using JT65 and JT9 now you won't have to wonder which is best on any particular day and time.

Here's Joe's post:

To: Users and potential users of WSJT-X
From: Joe Taylor, K1JT

I invite you to test-drive version 1.1 of WSJT-X. This version of the
program is "bi-lingual" -- it transmits and receives both JT9 and JT65
signals, switching between modes automatically as needed. The maximum
displayed bandwidth has been increased from 1 to 5 kHz. If your
receiver has an upper-sideband filter at least 4 kHz wide, on most bands
you can have all the JT65 *and* all the JT9 activity on screen at once,
available for making QSOs.

Other improvements since v1.0, r3323 include the following:

1. CAT control via DxLab Commander.
2. Improved GUI appearance, especially on Linux and OS X.
3. Compilable with Qt5 as well as Qt4.
4. Fixed occasional program crashes caused by receiving a message in the
form "call1 call2" (with no grid, report, etc.).
5. Improved handling of audio device selection in Linux.
6. Log QSO frequency, instead of dial frequency only.
7. Added Tx Power to ADIF log information, with option to retain between
QSOs.
8. Added option to retain between QSOs the Power and Comments fields for
ADIF and wsjtx logs.
9. Added optional antenna description for PSK Reporter.
10 Fixed a bug in handling of logged grid locator when none was
available on the double-clicked line.
11. Fixed a bug that caused small differences in the lengths of
transmitted symbols.
12. Tx message (highlighted in yellow) now includes a mode flag and the
audio frequency.
13. Added a spinner control for Rx Freq.
14. New on-screen button "Lock Tx=Rx" locks Tx and Rx frequencies together.
15. Allow COM port number greater than 9 (Windows only).
16. Don't clear DxGrid when user double-clicks on a message with no
grid, if the message's Tx call is same as DxCall.
17. Double-click on yellow Tx message sets frequency, but does nothing else.
18. Rationalized the logic of the CAT control indicator button. Now
colored grey/green/orange/red -- see User's Guide.


Even if you are already familiar with version 1.0, you should first read
the new online WSJT-X User's Guide:
http://www.physics.princeton.edu/pulsar/K1JT/WSJT-X_Users_Guide_v1.1.pdf

You can download the Windows installation package from
http://www.physics.princeton.edu/pulsar/K1JT/WSJTX_110r3459.exe

The program also runs well under Linux and OS X, but presently on these
platforms you must compile it yourself.

In many ways this release has been "cleaned up" and is more mature than
version 1.0. But with the JT65 capabilities it also contains a lot of
new code. Please send us bug reports and any suggestions for improvement.

A new version of JT-Alert (by VK3AMA) is in the works. At present your
JT9 activity will be handled as before -- but not your JT65 activity
with WSJT-X.

Finally: This is a group effort. My warmest thanks to AC6SL, G4KLA,
PY2SDR, and VK4BDJ (members of the WSJT Development Team), and to DJ0OT,
G4ILO, K0KC, K3WYC, NH7SR, W4TV, and VK3ACF, who been testing various
alpha versions of WSJT-X v1.1. Your input is greatly appreciated!

-- 73, Joe, K1JT

PS: If someone would like to cross-post this message to related email
lists, for example the JT65_HF Yahoo group, please feel free to do so.








------------------------------------

Yahoo!7 Groups Links

proposals for Text Messages: When you activate Text Messages, it will be good if JTMacros activated a special set of messages, that can be transferred to the text field. 

73 oz6dr

Laurie,

How does the user enable/disable receiving messages without turning off
the band activity?

73,

    ... Joe, W4TV


On 7/2/2013 6:36 PM, Laurie, VK3AMA wrote:

Tnx Rudy,

I see using the messages for simple things like..

   * Thanking for QSO, New State, DXCC etc.
   * Advising their Clock is off.
   * Advising their spotting on wrong band.
   * Advising another station is QRMing their signal.
   * Requesting a Band Change.

de Laurie VK3AMA

On 3/07/2013 7:54 AM, Rudy Benner wrote:

Its fine as is, great value.
rudy ve3bdr
*From:* Laurie, VK3AMA 
*Sent:* Tuesday, July 02, 2013 5:32 PM
*To:* Ham-Apps@... 
*Subject:* Re: [Ham-Apps] Text Messages

Just a few of points on the Text Message feature.

  * This was a "proof of concept" feature that accidentally got released. So I
    chose to leave it in-place. It is not complete and requires documentation.

  * This is not real-time and if there is a waiting message it is collected
    around the 30sec mark of the current minute when JTAlert retrieves Band
    Activity data from HamSpots. If you don't have the Band Activity display
    enabled, then you will never get a text message.

  * This is not a chat feature as only one message will be received per minute.

  * Messages are sent blind, there is no attempt to confirm a successful delivery.

  * If 2 or more users send a text message to the same Callsign in the current
    minute, only the newest message will be sent to the target Callsign as the
    code on HamSpots will only allow a single message. An existing message,
    waiting to be delivered will be overwritten by the newer message.

de Laurie VK3AMA

Tnx Rudy,

I see using the messages for simple things like..

* Thanking for QSO, New State, DXCC etc.
* Advising their Clock is off.
* Advising their spotting on wrong band.
* Advising another station is QRMing their signal.
* Requesting a Band Change.

de Laurie VK3AMA

On 3/07/2013 7:54 AM, Rudy Benner wrote:

Its fine as is, great value.
rudy ve3bdr
*From:* Laurie, VK3AMA <mailto:groups05@vkdxer.com>
*Sent:* Tuesday, July 02, 2013 5:32 PM
*To:* Ham-Apps@yahoogroups.com.au <mailto:Ham-Apps@yahoogroups.com.au>
*Subject:* Re: [Ham-Apps] Text Messages

Just a few of points on the Text Message feature.

* This was a "proof of concept" feature that accidentally got released. So I
chose to leave it in-place. It is not complete and requires documentation.

* This is not real-time and if there is a waiting message it is collected
around the 30sec mark of the current minute when JTAlert retrieves Band
Activity data from HamSpots. If you don't have the Band Activity display
enabled, then you will never get a text message.

* This is not a chat feature as only one message will be received per minute.

* Messages are sent blind, there is no attempt to confirm a successful delivery.

* If 2 or more users send a text message to the same Callsign in the current
minute, only the newest message will be sent to the target Callsign as the
code on HamSpots will only allow a single message. An existing message,
waiting to be delivered will be overwritten by the newer message.

de Laurie VK3AMA

Its fine as is, great value.

 

rudy ve3bdr

 

From: Laurie, VK3AMA

Sent: Tuesday, July 02, 2013 5:32 PM

To: Ham-Apps@...

Subject: Re: [Ham-Apps] Text Messages

 

 

Just a few of points on the Text Message feature.

• This was a "proof of concept" feature that accidentally got released. So I chose to leave it in-place. It is not complete and requires documentation.
  
  
• This is not real-time and if there is a waiting message it is collected around the 30sec mark of the current minute when JTAlert retrieves Band Activity data from HamSpots. If you don't have the Band Activity display enabled, then you will never get a text message.
  
  
• This is not a chat feature as only one message will be received per minute.
  
  
• Messages are sent blind, there is no attempt to confirm a successful delivery.
  
  
• If 2 or more users send a text message to the same Callsign in the current minute, only the newest message will be sent to the target Callsign as the code on HamSpots will only allow a single message. An existing message, waiting to be delivered will be overwritten by the newer message.

de Laurie VK3AMA