LogHX: English version

[RX4HX]

Hello and Happy New 2023 Year!

Randomly when I try to edit a QSO, the PC crashes, to restart it you have to turn off the power.

Here need more info. How are you trying to edit a QSO? Are you using the QSOManuallyEdit window? Is this window opening? Can you make video of crashes?

[Alde]

Here need more info. How are you trying to edit a QSO? [/QUOTE]

Hello, Dear Alexei, thank you for your prompt reply.

To edit a QSO, I double-click on the desired QSO, in the normal case I get the editing window, but randomly, in versions 708-715, instead of the editing window I get the timer icon and nothing else is possible to do.



73 de py5ej;
Pavanatti.

[Alde]

Hello and Happy New 2023 Year!


How are you trying to edit a QSO? Are you using the QSOManuallyEdit window? Is this window opening? Can you make video of crashes?

Hello, Dear Alexei.
Thank you very much for your attention.

At your request, I will describe the sequence:
In the main Log window, "Log PY5EJ.base:C:\ ... Log PY5EJ.lhx2" I select the desired QSO, with a single click, the line turns blue.

Then double click on that (blue) line to start editing;

In versions 707 and earlier, I always get the "QSO entry/manual editing" window, and everything works fine.

In versions 708-715, sometimes I don't get the "QSO entry/manual editing" window, as expected; instead, I get the timer icon, which stays there forever;

The crash is always random, and when it happens, is after double-click on the main Log window, "Log PY5EJ.base:C:\ ... Log PY5EJ.lhx2", on selected QSO (blue line) under versions 708-715.

HNY and 73 from py5ej,

[RX4HX]

To edit a QSO, I double-click on the desired QSO, in the normal case I get the editing window, but randomly, in versions 708-715, instead of the editing window I get the timer icon and nothing else is possible to do.

Try new prerelease -
http://rx4hx.qrz.ru/files/loghx/prer..._build_716.exe
Any changes?

[Alde]

Try new prerelease -
http://rx4hx.qrz.ru/files/loghx/prer..._build_716.exe
Any changes?

Hello, Dear Alexei.
Thank you for your attention.

Using prerelease 716, the problem for editing, "manual QSO entry/editing", still exists.

With differences:
Sometimes (random), after double-clicking on the desired QSO, I don't get the window "manual QSO entry/editing" as expected, instead the editing function becomes available from this point.
Apparently, everything goes on normally with the editing function disabled, (the timer icon does not appear, and the system does not crash, as it did in versions 708-715).

I am still testing with prerelease 716.

Thanks for your assistance.
Strong 73 from py5ej;
Pavanatti.

[IK2XDE]

Report on version 3.0 build from 707 to 716 (on previous builds was normal).

When starting the program, when the loading window opens,
and load these modules:

Loading Country.dat - successfully
DataModule created - successfully
DataBase Opened - successfully
MainFrom Created - successfully
Setup Cat: Only CW/PTT
CWForm created - successfully

at this point the loading seems to stop for 2-3 minutes, then resumes regularly and opens all the other modules


Begin Open PrevQSO
Prev QSO was opened - successfully
...ecc....
...ecc....

From my tests this problem occurs only if I use a computer with 3 monitors, where I normally load it on the second monitor.

If instead I use the log on a computer with only one monitor, the problem disappears and the loading is fluid and fast.

So I think the slowdown is due to using multiple monitors, ...as de loghx stops to think where to place the windows.

Alexey as always thanks for your attention I hope you can solve this problem.

73 de IK2XDE Andrea

- - - Добавлено - - -

ABOUT CTY.DAT

It would be useful if LOGHX automatically proposes the update of the CTY.DAT file
when and if new file will be available.

https://www.country-files.com/big-cty/

or new button to check it automatically.

We know that we can update it manually, when we want, but automatically is better......hi...!!

Thanks in advance.

73 de IK2XDE Andrea

[RX4HX]

instead the editing function becomes available from this point.

For more information - what does "editing function available" mean?

- - - Добавлено - - -

at this point the loading seems to stop for 2-3 minutes, then resumes regularly and opens all the other modules

It's not good!
Please download and install again 716 version
http://rx4hx.qrz.ru/files/loghx/prer..._build_716.exe
I add here info for loading.
After "CWForm created - successfully" must be other strings. This will help me localize the problem.

automatically proposes the update of the CTY.DAT file

I certainly thought about it. But there is a zip file with with various name: bigcty-20230104.zip
Problem is here.

[IK2XDE]

It's not good!
Please download and install again 716 version
http://rx4hx.qrz.ru/files/loghx/prer..._build_716.exe
I add here info for loading.
After "CWForm created - successfully" must be other strings. This will help me localize the problem.

OK instal and test new build 716

Loading Country.dat - successfully
DataModule created - successfully
DataBase Opened - successfully
MainFrom Created - successfully
Setup Cat: Only CW/PTT
CWForm created - successfully
GridForm created - successfully
Try load log database

at this point the loading seems to stop for 2-3 minutes, then resumes regularly and opens all the other modules

Log database opened - successfully
QSOEntry created - successfully
Begin Open PrevQSO
Prev QSO was opened - successfully
Begin open BandMap
BandMap was opened - successfully
Begin open Cluster
Cluster was opened - successfully
Begin open WorkedConfirmed
WorkedConfirmed was opened - successfully
Begin open QRZ.COM
QRZ.COm was opened - successfully
Start external programs

ON SINGLE MONITOR COMPUTER - ALL WORK FINE
ON 3 MONITOR COMPUTER - We have this problem only on first start, If I close the log and restart, no problem.
If I turn off computer , than restart computer and restart log...same problem....slow load at first start.
My log was with 130.000 qso....but I don't think this is the problem.
Some index corrupted...??

Hope in your solution.

73 de IK2XDE Andrea

- - - Добавлено - - -

If this will help:
Remember I run the log on the second monitor, not on the first monitor (pricipal)
And remember that I run log with this string: ...\LogHX\LogHX3.exe" /D=IK2XDE

73 de IK2XDE Andrea

[Alde]

[QUOTE=RX4HX;1926134]For more information - what does "editing function available" mean?

Sorry, Alexei for my mistake, I meant to say UNAVAILABLE;
The correct being "Instead, the editing function becomes unavailable", (nothing happens if you try a double click).

73 de py5ej,
Pavanatti.

[RX4HX]

nothing happens if you try a double click

May be QSOManuallyEntry widow opened beyond the boundaries of the screen.
What to do: try Shift + dbl click - for open window in left-top position of screen.

Try load log database

at this point the loading seems to stop for 2-3 minutes, then resumes regularly and opens all the other modules

Log database opened - successfully

There is only one action between these lines - opened log in log database. I don't think the monitor can somehow influence this.
Try copy database file to another computer and try opened.

My log was with 130.000 qso

130.000 - is not problem! 100%!

[IK2XDE]

There is only one action between these lines - opened log in log database. I don't think the monitor can somehow influence this.
Try copy database file to another computer and try opened.

Yes...just try,
on another computer, with single monitor, no problem, log start fast and fluid.

The problem appeared after the build 706, with the build 704 everything is ok.
PC - I7 9700k - 64Gb Ram - 1Tb SSD

If i return on build 704 all work fine.

Thanks

73 de IK2XDE Andrea.

[RX4HX]

on another computer, with single monitor, no problem, log start fast and fluid.

Do you use skin? If yes - disable skin and try without skin. May be here.

[IK2XDE]

Do you use skin? If yes - disable skin and try without skin. May be here.

OK, tomorrow I will try.
Thanks.

[Alde]

May be QSOManuallyEntry widow opened beyond the boundaries of the screen.
What to do: try Shift + dbl click - for open window in left-top position of screen.

Hello, Dear Alexei.
The unavailability problem, described, disappeared after restarting the program.
I am using build 716, and no longer have problems to edit a QSO (double-click > QSOManuallyEntry), now everything looks normal.

Please consider including in the Utilities > Find info ... > From the Internet >" HamRadio Outlet", address (https://www.hamradio.com/tools.cfm).

Thank you for your help and congratulations on a beautiful and useful LOG program.

Thanks,
73 de py5ej,
Pavanatti.

[IK2XDE]

At the end of the year I decided to make some statistics of my log,
and I encountered this problem in managing the WAE Award (Worked All Europe - DARC Award)
https://www.darc.de/en/der-club/refe...-country-list/

The problem is the recognition of these 4 entities valid for WAE but not for DXCC

4U1V - United Nations Vienna - ( DXCC 206 - Austria)
GM/S - Shetland Is. - (DXCC 279 - Scotland)
JW/B - Bear Is. - (DXCC 259 - Svalbard)
TA1 - European Turkey - (DXCC 390 - Turkey)


For these entities, unfortunately the diploma searches in the COUNTRY field, and finds what is foreseen for DXCC,
so for example 4U1VIC who operate from Vienna was considered as Austria and not as United Nation Vienna.
Same thing goes for JW9JKA who operate from Bear Is. but was considered as Svalbard....etc.....

What can we do to fix this problem...??

Thanks for help.
73 de IK2XDE Andrea.