Date   

locked Changing default logbook location

Robert <Robert@...>
 

Hello,
Can I change the default WSJT-X logbook location?
I use DropBox to backup my HRD LogBook, and it works fine because I can stipulate where I want my backup logbook file to go.
I would like to do the same thing with WSJT-X Logbook.
Is there a way?
--

Thanks,

Robert AC2MM


locked Re: LOTW/EQSL Flags - Resolved

Michael Black
 

And also the popup on the callsign showed LOTW too so it apparently isn't seeing that time limit flag either.
That's what confused me...hover over the callsign and it showed LOTW but no flag.

Thanks Laurie.

Mike




On Sunday, February 17, 2019, 7:17:08 PM CST, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 18/02/2019 8:43 am, HamApps Support (VK3AMA) via Groups.Io wrote:
On 17/02/2019 3:34 pm, Michael Black via Groups.Io wrote:
I did a local loopback to test this.  Flag is right in the Decodes History but not the call slot.

Mike

Mike,

I can't reproduce here. Flags are correctly shown (using the V47KA you tested with), Own Call with Wanted DXCC triggered.

Send me a support request so I can test using your Config file.

de Laurie VK3AMA
Mike,

The reason the LoTW flag is not being displayed in the JTAlert main display is due to you having a one year time limit filter set for LoTW flagging and the callsign in question, V47KA, last uploaded to LoTW on 2016-05-03, from the Callsign database, outside that one year limit. I note that he has recently uploaded to LoTW and that will be reflected in the next database update.

eQSL flags are not shown because you have them turned off.

The Decodes History V3 that your running currently doesn't obey the LoTW flag time limit filtering and thus showed the flag.

de Laurie VK3AMA




locked Re: LOTW/EQSL Flags - Resolved

HamApps Support (VK3AMA)
 

On 18/02/2019 8:43 am, HamApps Support (VK3AMA) via Groups.Io wrote:
On 17/02/2019 3:34 pm, Michael Black via Groups.Io wrote:
I did a local loopback to test this.  Flag is right in the Decodes History but not the call slot.

Mike

Mike,

I can't reproduce here. Flags are correctly shown (using the V47KA you tested with), Own Call with Wanted DXCC triggered.

Send me a support request so I can test using your Config file.

de Laurie VK3AMA
Mike,

The reason the LoTW flag is not being displayed in the JTAlert main display is due to you having a one year time limit filter set for LoTW flagging and the callsign in question, V47KA, last uploaded to LoTW on 2016-05-03, from the Callsign database, outside that one year limit. I note that he has recently uploaded to LoTW and that will be reflected in the next database update.

eQSL flags are not shown because you have them turned off.

The Decodes History V3 that your running currently doesn't obey the LoTW flag time limit filtering and thus showed the flag.

de Laurie VK3AMA




locked Re: Sicily vis-a-vis Marathon (and Italian Africa)

HamApps Support (VK3AMA)
 

Steve,

Good stuff.

FWIW, this is a timing issue as JTAlert reads the disk-based country database into memory so that repeated access to the database during the Scan are the fastest they can be and avoids any disk-thrashing with many thousands of sql queries done against the database if it remained disk-based. Delaying the scan allowed for the database-to-memory import to have been completed resulting in correct lookups.

This has been corrected for the next release.

de Laurie VK3AMA

On 18/02/2019 9:44 am, Steve, N3SL wrote:
Ta da!  That's all it took.....

On Sun, Feb 17, 2019 at 3:46 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 18/02/2019 8:19 am, Steve, N3SL wrote:
I see this has been reported before, but the thread stops without a resolution.  I presume that means it's just an issue to "live with."  I'm guessing it's because DXLab does NOT recognize IT9 or IH9 as anything other than Italy, so every "scan and rebuild" wipes out the IT9 and IH9 "worked" status, and spots again show as needed.  Not critical, obviously....

Steve, N3SL
Steve,

Please try this...
Wait ~15 seconds after opening the Settings in preparation for the Scan Log, than run the Scan. Is the IT9 status now correct?

de Laurie VK3AMA


locked Re: Sicily vis-a-vis Marathon (and Italian Africa)

Steve, N3SL
 

Ta da!  That's all it took.....


On Sun, Feb 17, 2019 at 3:46 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 18/02/2019 8:19 am, Steve, N3SL wrote:
I see this has been reported before, but the thread stops without a resolution.  I presume that means it's just an issue to "live with."  I'm guessing it's because DXLab does NOT recognize IT9 or IH9 as anything other than Italy, so every "scan and rebuild" wipes out the IT9 and IH9 "worked" status, and spots again show as needed.  Not critical, obviously....

Steve, N3SL
Steve,

Please try this...
Wait ~15 seconds after opening the Settings in preparation for the Scan Log, than run the Scan. Is the IT9 status now correct?

de Laurie VK3AMA


locked Re: Sicily vis-a-vis Marathon (and Italian Africa)

Steve, N3SL
 

OK, Dave, that part was already done, and yes, the IT9 "region" is displayed.  So my "guess" was incorrect. 
In another message (you probably have seen) Laurie says to "wait 15sec" after clicking on settings and then do a "scan and rebuild."  Lo and behold.....

Thanks, Gentlemen.

On Sun, Feb 17, 2019 at 3:32 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

I see this has been reported before, but the thread stops without a resolution.  I presume that means it's just an issue to "live with."  I'm guessing it's because DXLab does NOT recognize IT9 or IH9 as anything other than Italy

+ That's false, Steve.

+ On the Awards tab of DXKeeper's Configuration window, Configuration window, check the "CQ, WAE, Holyland region select" box in the Other awards panel.

+ Then type IT9DX into DXKeeper's Capture window, and strike the Enter key. Note that the Capture window's Region selector is set to IT9, indicating a "CQ Country" of Sicily. All CQ and WAE countries are defined as Regions of DXCC entities. Callsign analysis correctly sets the region, as it did for IT9DX.

+ See

<https://www.dxlabsuite.com/dxlabwiki/CQCountryQSOLogging>

+ Applications like JT-Alert that log QSOs directly to DXKeeper can specify the QSO's Region using the APP_DXKeeper_Region field.

       73,

          Dave, AA6YQ






locked Re: Sicily vis-a-vis Marathon (and Italian Africa)

HamApps Support (VK3AMA)
 

On 18/02/2019 8:19 am, Steve, N3SL wrote:
I see this has been reported before, but the thread stops without a resolution.  I presume that means it's just an issue to "live with."  I'm guessing it's because DXLab does NOT recognize IT9 or IH9 as anything other than Italy, so every "scan and rebuild" wipes out the IT9 and IH9 "worked" status, and spots again show as needed.  Not critical, obviously....

Steve, N3SL
Steve,

Please try this...
Wait ~15 seconds after opening the Settings in preparation for the Scan Log, than run the Scan. Is the IT9 status now correct?

de Laurie VK3AMA


locked Re: LOTW/EQSL Flags

HamApps Support (VK3AMA)
 

On 17/02/2019 3:34 pm, Michael Black via Groups.Io wrote:
I did a local loopback to test this.  Flag is right in the Decodes History but not the call slot.

Mike
Mike,

I can't reproduce here. Flags are correctly shown (using the V47KA you tested with), Own Call with Wanted DXCC triggered.

Send me a support request so I can test using your Config file.

de Laurie VK3AMA


locked Re: Sicily vis-a-vis Marathon (and Italian Africa)

Dave AA6YQ
 

+ AA6YQ comments below

I see this has been reported before, but the thread stops without a resolution. I presume that means it's just an issue to "live with." I'm guessing it's because DXLab does NOT recognize IT9 or IH9 as anything other than Italy

+ That's false, Steve.

+ On the Awards tab of DXKeeper's Configuration window, Configuration window, check the "CQ, WAE, Holyland region select" box in the Other awards panel.

+ Then type IT9DX into DXKeeper's Capture window, and strike the Enter key. Note that the Capture window's Region selector is set to IT9, indicating a "CQ Country" of Sicily. All CQ and WAE countries are defined as Regions of DXCC entities. Callsign analysis correctly sets the region, as it did for IT9DX.

+ See

<https://www.dxlabsuite.com/dxlabwiki/CQCountryQSOLogging>

+ Applications like JT-Alert that log QSOs directly to DXKeeper can specify the QSO's Region using the APP_DXKeeper_Region field.

73,

Dave, AA6YQ


locked Sicily vis-a-vis Marathon (and Italian Africa)

Steve, N3SL
 

I see this has been reported before, but the thread stops without a resolution.  I presume that means it's just an issue to "live with."  I'm guessing it's because DXLab does NOT recognize IT9 or IH9 as anything other than Italy, so every "scan and rebuild" wipes out the IT9 and IH9 "worked" status, and spots again show as needed.  Not critical, obviously....

Steve, N3SL


locked Re: Items on Left of Title-Bar area ?

KD7YZ Bob
 

On 2/16/2019 21:44, HamApps Support (VK3AMA) wrote:

I am guessing your on Windows 10.
right you are.

the 'alternative' fixed it .. tnx



--
Bob KD7YZ
AMSAT LM #901


locked Re: LOTW/EQSL Flags

Michael Black
 

I did a local loopback to test this.  Flag is right in the Decodes History but not the call slot.

Inline image


Inline image

Mike



On Saturday, February 16, 2019, 6:31:35 PM CST, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 16/02/2019 7:57 am, Michael Black via Groups.Io wrote:
The LOTW/EQSL Flags aren't being shown on DXCC-color-coded calls in the call slots.

I don't think you need debug info as this should be fairly easy to check & duplicate.

de Mike W9MDB
Mike,


What do the same Callsigns in the Decodes History show, are they also missing the flags?

de Laurie VK3AMA


locked Re: Items on Left of Title-Bar area ?

HamApps Support (VK3AMA)
 

On 17/02/2019 12:08 pm, KD7YZ Bob wrote:
I wonder what is supposed to be of the area to the left of |Sound On|?

if no attachments are allowed, the, what-I-See on the Title-Bar is that
to the left of |Sound ON| I see a w  (w), farther to the left of that
"w" is my windows background image

did a re-install. Deleted the Config-sq,,, folder in AppData, an so forth.

Bob KD7YZ
I am guessing your on Windows 10. Some users have experienced incorrectly placed or missing menus in the title-bar. The cause is unknown and has not been reproducible in my tests.

The only fix is to install the "Alternate Layout" build of JTAlert. Download from HamApps.com

de Laurie VK3AMA


locked Items on Left of Title-Bar area ?

KD7YZ Bob
 

I wonder what is supposed to be of the area to the left of |Sound On|?

if no attachments are allowed, the, what-I-See on the Title-Bar is that
to the left of |Sound ON| I see a w (w), farther to the left of that
"w" is my windows background image


did a re-install. Deleted the Config-sq,,, folder in AppData, an so forth.


--
73
Bob KD7YZ
AMSAT LM #901


locked Re: LOTW/EQSL Flags

HamApps Support (VK3AMA)
 

On 16/02/2019 7:57 am, Michael Black via Groups.Io wrote:
The LOTW/EQSL Flags aren't being shown on DXCC-color-coded calls in the call slots.

I don't think you need debug info as this should be fairly easy to check & duplicate.

de Mike W9MDB
Mike,

What do the same Callsigns in the Decodes History show, are they also missing the flags?

de Laurie VK3AMA


locked Re: LOTW/EQSL Flags

Michael Black
 

I may be confusing DX with the red-colored tagged for my callsign...might be just that one not seeing the flags when I'm in a QSO with them.

I do have only the LOTW flags checked right now.

Mike




On Friday, February 15, 2019, 4:47:37 PM CST, Jim Nuytens <jim.kj3n@...> wrote:


I'd be curious to know how you have your JT-Alert set up. I'm not seeing this problem. I get the flags on everything.

On 2/15/2019 20:57, Michael Black via Groups.Io wrote:
Running 2.12.10 Build 0015

The LOTW/EQSL Flags aren't being shown on DXCC-color-coded calls in the call slots.

I don't think you need debug info as this should be fairly easy to check & duplicate.

de Mike W9MDB


Virus-free. www.avg.com


locked Re: LOTW/EQSL Flags

Jim Nuytens
 

I'd be curious to know how you have your JT-Alert set up. I'm not seeing this problem. I get the flags on everything.

On 2/15/2019 20:57, Michael Black via Groups.Io wrote:
Running 2.12.10 Build 0015

The LOTW/EQSL Flags aren't being shown on DXCC-color-coded calls in the call slots.

I don't think you need debug info as this should be fairly easy to check & duplicate.

de Mike W9MDB


Virus-free. www.avg.com


locked LOTW/EQSL Flags

Michael Black
 

Running 2.12.10 Build 0015

The LOTW/EQSL Flags aren't being shown on DXCC-color-coded calls in the call slots.

I don't think you need debug info as this should be fairly easy to check & duplicate.

de Mike W9MDB





locked Re: Listed contacts are always late

Robert <Robert@...>
 

Wow, now that was really cool, thank you.

Robert AC2MM


On 2/14/2019 11:03 AM, Carey Fisher wrote:
You could check the CQ Only block on the front page of WSJTX.

--
Carey Fisher



locked Re: Listed contacts are always late

Carey, WB4HXE
 

Just check CQ Only on the front page of WSJTX.

On Thu, Feb 14, 2019 at 11:23 AM WB5JJJ - George <wb5jjj@...> wrote:
If you are using JTAlert, set it to show those calling CQ and not worked B4 on the ALERTS>>FILTERS section, check CQ only and hide B4, that will show just the ones that you really want to see instead of everything that WSJTx already shows you in the Band Activity window. 
--
73's
George - WB5JJJ



--
Carey Fisher

15181 - 15200 of 38542