Date   

locked Re: Interesting inconsistency

John Petrocelli
 

Hello Laurie,

   Perhaps my Names for the windows is not the same as yours.
Yet it seems all good now.

Thanks,
John
John R. Petrocelli - WA2HIP
¶¶¶¶¶¶¶¶¶¶
Primary Home Page:
   http://wa2hip.com
On 2021-05-05 07:07, HamApps Support (VK3AMA) wrote:
On 5/05/2021 4:22 pm, John Petrocelli via groups.io wrote:
  The "Main Window" is the one with the Menu at the top

   The "Callsign Window" is the one where the decoded callsigns all show.

Are you referring to your QSO partner callsign when it is displayed on the main window, to the left of the log fields? That's the only place I can find with a callsigns context menu. If so, the differences between it and the new Callsigns window are due to how they are coded. When I added the user-customizable context menu to the Callsigns window, I chose not to try and replicate that in the old JTAlert window. Eventually, it will disappear, so would have been a waste of effort writing code in the old code-base that is being replaced with the new code with each new release. Consider it an "Operational Quirk" of the JTAlert 2.50.x series, which is a hybrid of the old and the new code-bases.

de Laurie VK3AMA



Virus-free. www.avast.com


locked All Worked B4 call sign displays are Displaying Needed, but Have Been Worked. #FT8

Brian Kassel K7RE
 

The call sign "worked B4" works as it should,
But no matter what I have tried, the States, VE and DXCC stations are always in Yellow
in both the calls in the Band Activity Window and the other window that displays calls and info.

(Yellow is the default color for NOT worked B4, and also my choice)

I tried the "Rebuild Database" many times.
Scrolling up on the list after the scan does show the correct totals os stations that have been worked on each band.




I am using the Standard ADIF File and JTAlert 2.50.1, with WSJTX 2.3.1.

JTAlert
    Settings
        Manage Settings
                Alerts
                    Wanted US State
                        Enable Wanted US State Alert (Checked)
                        Default Wave File Path
                        Sample Set to Yellow
                Logging
                    Standard ADIF File
                        Enable Standard ADIF File Logging (Checked)
                        C:\Users\Brian\AppData\Local\WSJT-X\wsjtx_log.adi (In red, uneditable)
                        Log File
                        C;\Users\Brian\Desktop\FT8 Log Spearfish.adi
                Log B4 Database File
                C:\Users\Brian\AppData\Local\HamApps\K7RE\logs\JTAlertX\B4logV2.MDB (Greyed, uneditable)

Could it be that the MDB database is corrupted?
If so, how do I fix that issue.

Thanks for reading this, and thanks for the wonderful program.
                   


locked Re: Sending QSO to eQSL

je6woq@...
 

Laurie,

Thanks for your advice! I worked finally.

What was confusing was "QTH Nickname".

"QTH Nickname" requires you to set the one that is defined in your eQSL
profile. But I misunderstood that "QTH Nickname" meant QTH and Nickname,
and I did not set the one as defined by "QTH Nickname" in eQSL.

What made this mistake was that I first looked at the same function of
JTDX in Japanese translation version. The translation says "QTH and
Nickname" in Japanese. So I believed it would mean that it is for "QTH
and Nickname", not the one as defined in eQSL as "QTH Nickname".

Anyway, my problem is solved and thank you very much for your advice.
I think the Japanese translation of JTDX for this portion needs to be
improves so as not to confuse people.

73

JE6WOQ
Max

I have been trying to set up JTAlert to automatically upload QSO
data to eQSL. I added my eQSL account name and the password on
JTAlert setting and checked "enable" box @ Settings/Manage Setting/Web
Service/Online Logbooks. But my QSO data do not seem to be appearing
in the OutBox of the eQSL site. Is there anything else that I need to
set other than what are described above? Your advice will be greatly
appreciated. 73 JE6WOQ Max

You need to fill in all 3 pieces of data, Callsign, Password and Nickname.

de Laurie VK3AMA


locked Re: Sending QSO to eQSL

HamApps Support (VK3AMA)
 

On 5/05/2021 8:41 pm, je6woq@... wrote:
I have been trying to set up JTAlert to automatically upload QSO data to eQSL.

I added my eQSL account name and the password on JTAlert setting and
checked "enable" box @ Settings/Manage Setting/Web Service/Online
Logbooks. 

But my QSO data do not seem to be appearing in the OutBox of the eQSL
site.

Is there anything else that I need to set other than what are described
above?

Your advice will be greatly appreciated.

73

JE6WOQ
Max

You need to fill in all 3 pieces of data, Callsign, Password and Nickname.

de Laurie VK3AMA


locked Sending QSO to eQSL

je6woq@...
 

Hi

I have been trying to set up JTAlert to automatically upload QSO data to eQSL.

I added my eQSL account name and the password on JTAlert setting and
checked "enable" box @ Settings/Manage Setting/Web Service/Online
Logbooks.

But my QSO data do not seem to be appearing in the OutBox of the eQSL
site.

Is there anything else that I need to set other than what are described
above?

Your advice will be greatly appreciated.

73

JE6WOQ
Max


locked Re: Interesting inconsistency

HamApps Support (VK3AMA)
 

On 5/05/2021 4:22 pm, John Petrocelli via groups.io wrote:
  The "Main Window" is the one with the Menu at the top

   The "Callsign Window" is the one where the decoded callsigns all show.

Are you referring to your QSO partner callsign when it is displayed on the main window, to the left of the log fields? That's the only place I can find with a callsigns context menu. If so, the differences between it and the new Callsigns window are due to how they are coded. When I added the user-customizable context menu to the Callsigns window, I chose not to try and replicate that in the old JTAlert window. Eventually, it will disappear, so would have been a waste of effort writing code in the old code-base that is being replaced with the new code with each new release. Consider it an "Operational Quirk" of the JTAlert 2.50.x series, which is a hybrid of the old and the new code-bases.

de Laurie VK3AMA


locked Re: Interesting inconsistency

John Petrocelli
 

Hello,

  The "Main Window" is the one with the Menu at the top

   The "Callsign Window" is the one where the decoded callsigns all show.

   I clicked on the "gear" icon and see those settings now. Thanks for setting my thinking straight.


   Hopefully, the other anomaly that I mentioned 2 days ago regarding the QSO history showing as FT4 when in FT8 mode will be resolved in the next release.

Thanks again for doing such a GREAT JOB !!

John
John R. Petrocelli - WA2HIP
¶¶¶¶¶¶¶¶¶¶
Primary Home Page:
   http://wa2hip.com
On 2021-05-05 06:13, HamApps Support (VK3AMA) wrote:
On 5/05/2021 3:48 pm, John Petrocelli via groups.io wrote:

   I notice that the drop-down on right-clicking the callsign is different when right-clicking on the Main Window vs. the Callsign Window.

  On the Main Window there are 14 items in the drop down.
  On the Callsign Window there are only 4 items on the drop-down.

  I am running version 2.50.1 and I believe that there were 14 items in both the mentioned actions.

  Am I missing something here ??

Thanks in advance.
John
-- 

What is this "main window" you're referring to? The Main JTAlert window doesn't have callsigns to display any longer.

As for the Callsigns window, as of 2.50.1, which menu entries in the right-click context menu are visible is controlled by the end-user. Look under the Options popup (via gear icon), "Menus" section.

de Laurie VK3AMA




Virus-free. www.avast.com


locked Re: Interesting inconsistency

HamApps Support (VK3AMA)
 

On 5/05/2021 3:48 pm, John Petrocelli via groups.io wrote:

   I notice that the drop-down on right-clicking the callsign is different when right-clicking on the Main Window vs. the Callsign Window.

  On the Main Window there are 14 items in the drop down.
  On the Callsign Window there are only 4 items on the drop-down.

  I am running version 2.50.1 and I believe that there were 14 items in both the mentioned actions.

  Am I missing something here ??

Thanks in advance.
John
-- 

What is this "main window" you're referring to? The Main JTAlert window doesn't have callsigns to display any longer.

As for the Callsigns window, as of 2.50.1, which menu entries in the right-click context menu are visible is controlled by the end-user. Look under the Options popup (via gear icon), "Menus" section.

de Laurie VK3AMA



locked Interesting inconsistency

John Petrocelli
 

Hello,

   I notice that the drop-down on right-clicking the callsign is different when right-clicking on the Main Window vs. the Callsign Window.

  On the Main Window there are 14 items in the drop down.
  On the Callsign Window there are only 4 items on the drop-down.

  I am running version 2.50.1 and I believe that there were 14 items in both the mentioned actions.

  Am I missing something here ??

Thanks in advance.
John
-- 


John R. Petrocelli - WA2HIP
¶¶¶¶¶¶¶¶¶¶
Primary Home Page:
   http://wa2hip.com

Virus-free. www.avast.com


locked Re: 2.5.0 -- AutoIt Error

HamApps Support (VK3AMA)
 

On 4/05/2021 5:16 pm, Richard, PD3RFR wrote:
Some steps, not in chronical order and maybe missing some steps:
Installed JTAlert 2.5.0.1., de-installed it, installed older version of JT (same error other line), reinstalled latest version. Deleted config, put config back, upgraded HRD in meanwhile, rebooted the PC several times.
Took a while. I'm happy now, sorry I can't reproduce.. or have the right solution. I think it had to do with the config.

Richard, tnx for the update.

I also suspect it is a config issue, but that should have been evident when starting JTAlert without a config, unless you deleted the wrong file. There are likely 2 config.sqlite files in your %localappdata%\HamApps\ directory tree. One under a JTAlertX directory and one under a JTAlert directory. The one under JTAlert is old and no longer used. The correct file is under the JTAlertX directory.

FWIW, the whole directory structure and files locations will be changing as JTAlert incorporates the features of the JTAlertV3 (unreleased) code-base. Eventually the location of the user setting files will be user-settable and no longer tied to the %localappdata% area.

de Laurie VK3AMA


locked Re: JTAlert problem with Scan and Rebuild database

HamApps Support (VK3AMA)
 

On 5/05/2021 1:47 am, Dennis wrote:
can't get JAlert to Scan and rebuild database

In the JTAlert Settings, "Logging -> DXLab DXKeeper" section, is the correct log file displayed?

Also, I strongly suggest you update your JTAlert version, 2.16.4 is over 12 months old.

de Laurie VK3AMA


locked Re: CHat support without WSJTx

HamApps Support (VK3AMA)
 

On 5/05/2021 1:52 am, Franco wrote:
There is absolutely no possibility to use the JTalert CHAT (F5) without always having to start WSJTx first and then quit, why don't I use that??

Thanks for info
Franco

Messaging (Chat) is built into JTAlert, it cannot be run without JTAlert running. JTAlert needs to find a copy of WSJT-X running before it can finish its startup. Thus it is not possible to bring up the JTAlert Messaging without WSJT-X running.

de Laurie VK3AMA


locked Re: Callsign window doesn't minimize

HamApps Support (VK3AMA)
 

On 4/05/2021 11:54 am, WU9D wrote:

Try unticking “Show in Taskbar”. The window then doesn’t minimize. Tick the box and its behavior is like the others. Strange.


That is standard Windows behavior when minimizing a window and the show in taskbar setting is turned off. Since Windows cannot minimize to the taskbar, it minimizes it to an entry to just above the taskbar on the left. Here is mine when the Messaging, Callsigns and Activity windows are all minimized when the show in taskbar setting is off.

   

Windows does this so you still have access to a minimized window that is not visible in the TaskBar.
There is nothing that I can do about this standard Windows behavior.

de Laurie VK3AMA
 


locked Re: v2.50.1 Second or third FT8 contact logged as FT8 with FT4 sub-mode. - DEFECT Confirmed

on5po
 


Voici la solution, qui a été donnée précédemment, et qui fonctionne  


ON5PO,


De : Support@HamApps.groups.io <Support@HamApps.groups.io> de la part de Jacques Corbu <f1vev@...>
Envoyé : mardi 4 mai 2021 17:21
À : Support@HamApps.groups.io <Support@HamApps.groups.io>
Objet : Re: [HamApps] v2.50.1 Second or third FT8 contact logged as FT8 with FT4 sub-mode. - DEFECT Confirmed
 
Hello 

Ran FT8 this afternoon and  it got logged as FT8 with FT4 submode after a few contacts  cannot say how many . Ic7300  HRD logbook on SQL  and V2.5 JTAlert 

WSJTX frequencies are correct etc  not doubt will be resolved shortly as defect is confirmed Cheers F1VEV Jacques  


locked Re: CHat support without WSJTx

Franco
 

HI ALL, 

There is absolutely no possibility to use the JTalert CHAT (F5) without always having to start WSJTx first and then quit, why don't I use that??

Thanks for info
Franco


locked Re: JTAlert problem with Scan and Rebuild database

Dennis
 

DXView running, DXCC updated, DXKeeper updated no error bu still can't get JAlert to Scan and rebuild database.  :(


locked Re: JTAlert problem with Scan and Rebuild database

Dennis
 

Ok I don';t know what happened but I shut everything down and restarted.  No more error logs.


locked Re: v2.50.1 Second or third FT8 contact logged as FT8 with FT4 sub-mode. - DEFECT Confirmed

Jacques Corbu
 

Hello 

Ran FT8 this afternoon and  it got logged as FT8 with FT4 submode after a few contacts  cannot say how many . Ic7300  HRD logbook on SQL  and V2.5 JTAlert 

WSJTX frequencies are correct etc  not doubt will be resolved shortly as defect is confirmed Cheers F1VEV Jacques  


locked Re: SSL installation

David Gould
 

Thanks that is the info I wanted.
73,
Dave G3UEG


WSJTX and the procedure for installing SSL is documented in the Users
Guide (Help) section 3.2.

Open SSL is only required for loading the LotW Users Data ...

73,

... Joe, W4TV
Hide quoted text


locked Re: JTAlert problem with Scan and Rebuild database

Dennis
 

I updated all the DXCC files, DXkeeper , DXview.  Still getting Error log though.   

821 - 840 of 35468