|
This release includes the following changes -
Changes made to the Previous QSO Window so that a left click on either the BAND or MODE column header sorts the previous QSOs by Band or Mode.
Fixed a referential integrity bug with WAZ and WAS award statistics. After installing this update, you must recalculate the statistics for all your logbooks.
A new feature has been added to highlight (in bold letters and color of your choice) DX Spots of DXpeditiions listed by DX-World at
Look at sections 14.2.3 and 14.4 of the help file for details. This is all new code, expect teething problems.
?
Enjoy, 73.
|
.? Sorry for the slight delay.? I was out logging ... with a chainsaw, not a keyboard.
Hey I noticed that there have been no ?for a couple of years.? Would anyone care to update the world on all the sexy new features Bob has added recently??
73 Gary? ?beater/tester &?
Honor Roll &? checker
This release includes the following changes -
Changes made to the Previous QSO Window so that a left click on either the BAND or MODE column header sorts the previous QSOs by Band or Mode.
Fixed a referential integrity bug with WAZ and WAS award statistics. After installing this update, you must recalculate the statistics for all your logbooks.
A new feature has been added to highlight (in bold letters and color of your choice) DX Spots of DXpeditiions listed by DX-World at
Look at sections 14.2.3 and 14.4 of the help file for details. This is all new code, expect teething problems.
?
Enjoy, 73.
|
Hello. Thanks for this new release. I found some that is not more working.on this release.
Insert a partial callsing in the Logbook Entry Window, then in the Worked/Confirmed Window we can see the status of that Country/DXCC on all Bands/Modes. When I click on a Mode of an only Worked slot for that Band, the new Windoow that open does not more show the QSO (or QSOs) made with that Country/DXCC on that specific Band/Mode. So we cannot know what is (or what are) the callsing/cllsigns we worked (before) on that specific Band/Mode.
See here:
I inserted "9H" and I ciicked on "CW" cell on the CW/15m, the new window open but des not show the prevoius QSOS/QSOs made with all "9H" on 15m CW.
For test I clicked also on the combination "PHO" on the cell 20m (confirmed) and this is the result:
So it looks like now we can see only the confimred QSOs and not also the Worked ones. I already did recalculate statistics.
Thanks.
On Sunday, December 1, 2024 at 01:21:18 AM GMT+1, Bob via groups.io <k4cy@...> wrote:
This release includes the following changes -
Changes made to the Previous QSO Window so that a left click on either the BAND or MODE column header sorts the previous QSOs by Band or Mode.
Fixed a referential integrity bug with WAZ and WAS award statistics. After installing this update, you must recalculate the statistics for all your logbooks.
A new feature has been added to highlight (in bold letters and color of your choice) DX Spots of DXpeditiions listed by DX-World at
Look at sections 14.2.3 and 14.4 of the help file for details. This is all new code, expect teething problems.
?
Enjoy, 73.
|
I think you have a serious problem ... everything works normally! Try to redo the recalculation of the statistics.
Good luck
Hello.
Thanks for this new release.
I found some that is not more working.on this release.
Insert a partial callsing in the Logbook Entry Window, then in the Worked/Confirmed Window we can see the status of that Country/DXCC on all Bands/Modes.
When I click on a Mode of an only Worked slot for that Band, the new Windoow that open does not more show the QSO (or QSOs) made with that Country/DXCC on that specific Band/Mode.
So we cannot know what is (or what are) the callsing/cllsigns we worked (before) on that specific Band/Mode.
See here:
I inserted "9H" and I ciicked on "CW" cell on the CW/15m, the new window open but des not show the prevoius QSOS/QSOs made with all "9H" on 15m CW.
For test I clicked also on the combination "PHO" on the cell 20m (confirmed) and this is the result:
So it looks like now we can see only the confimred QSOs and not also the Worked ones.
I already did recalculate statistics.
Thanks.
On Sunday, December 1, 2024 at 01:21:18 AM GMT+1, Bob via groups.io <k4cy@...> wrote:
This release includes the following changes -
Changes made to the Previous QSO Window so that a left click on either the BAND or MODE column header sorts the previous QSOs by Band or Mode.
Fixed a referential integrity bug with WAZ and WAS award statistics. After installing this update, you must recalculate the statistics for all your logbooks.
A new feature has been added to highlight (in bold letters and color of your choice) DX Spots of DXpeditiions listed by DX-World at
Look at sections 14.2.3 and 14.4 of the help file for details. This is all new code, expect teething problems.
?
Enjoy, 73.
|
It works as expected for me. SeventyThree(s).
On 12/01/2024 2:19 AM EST Fabio IZ8MBW via groups.io <iz8mbw@...> wrote:
?
?
Hello.
Thanks for this new release.
I found some that is not more working.on this release.
?
Insert a partial callsing in the Logbook Entry Window, then in the Worked/Confirmed Window we can see the status of that Country/DXCC on all Bands/Modes.
When I click on a Mode of an only Worked slot for that Band, the new Windoow that open does not more show the QSO (or QSOs) made with that Country/DXCC on that specific Band/Mode.
So we cannot know what is (or what are) the callsing/cllsigns we worked (before) on that specific Band/Mode.
?
?
See here:
?
 <5cea6e90-2a3c-7adc-5740-7ee1332e007b@...>">
?
I inserted "9H" and I ciicked on "CW" cell on the CW/15m, the new window open but des not show the prevoius QSOS/QSOs made with all "9H" on 15m CW.
?
?
For test I clicked also on the combination "PHO" on the cell 20m (confirmed) and this is the result:
 <8be19310-257d-9b9c-af5c-0edf2fe39173@...>">
?
So it looks like now we can see only the confimred QSOs and not also the Worked ones.
I already did recalculate statistics.
?
?
?
Thanks.
?
?
?
On Sunday, December 1, 2024 at 01:21:18 AM GMT+1, Bob via groups.io <k4cy@...> wrote:
?
?
This release includes the following changes -
Changes made to the Previous QSO Window so that a left click on either the BAND or MODE column header sorts the previous QSOs by Band or Mode.
Fixed a referential integrity bug with WAZ and WAS award statistics. After installing this update, you must recalculate the statistics for all your logbooks.
A new feature has been added to highlight (in bold letters and color of your choice) DX Spots of DXpeditiions listed by DX-World at
Look at sections 14.2.3 and 14.4 of the help file for details. This is all new code, expect teething problems.
?
Enjoy, 73.
|
I've already run the statistics recalculation twice and both
times the Lg32 shut down before the process was complete. 262k
QSOs.
73?? Vytas?? LZ2VQ
2024-12-01 02:20, Bob via groups.io
ra??:
toggle quoted message
Show quoted text
Fixed a
referential integrity bug with WAZ and WAS award statistics. After
installing this update, you must recalculate the statistics
for all your logbooks.
|
After running it for the third time, the statistics recalculation
was successful with a few stops. I didn't understand the essence
of the error, I reviewed the data of the specified QSO, as if
everything was in order.
I noticed that Cherry-picking event viewer writes in very large
letters. I do not know how to reduce them.
73?? Vytas?? LZ2VQ
2024-12-01 15:46, Vytas VQ via
groups.io ra??:
toggle quoted message
Show quoted text
I've already run the statistics recalculation twice and both
times the Lg32 shut down before the process was complete. 262k
QSOs.
73?? Vytas?? LZ2VQ
|
Vytas Rollback to 4.0.329. If it works then update to 4.0.330 again.
On 2024-12-02 月 16:40:43, Vytas VQ via groups.io <v.kudelis@...> wrote:
After running it for the third time, the statistics recalculation
was successful with a few stops. I didn't understand the essence
of the error, I reviewed the data of the specified QSO, as if
everything was in order.
I noticed that Cherry-picking event viewer writes in very large
letters. I do not know how to reduce them.
73?? Vytas?? LZ2VQ
2024-12-01 15:46, Vytas VQ via
groups.io ra??:
I've already run the statistics recalculation twice and both
times the Lg32 shut down before the process was complete. 262k
QSOs.
73?? Vytas?? LZ2VQ
|
After reverting to v.329, the font size in the Cherry-picking
event viewer did not change.
73?? Vytas?? LZ2VQ
2024-12-02 09:47, ja1nlx via groups.io
ra??:
toggle quoted message
Show quoted text
Vytas
Rollback to 4.0.329.
If it works then update to 4.0.330 again.
On 2024-12-02 月
16:40:43, Vytas VQ via groups.io
<v.kudelis@...> wrote:
After running it for the third time, the statistics
recalculation was successful with a few stops. I didn't
understand the essence of the error, I reviewed the data
of the specified QSO, as if everything was in order.
I noticed that Cherry-picking event viewer writes in
very large letters. I do not know how to reduce them.
73?? Vytas?? LZ2VQ
2024-12-01 15:46, Vytas VQ
via groups.io ra??:
I've already run the statistics recalculation twice
and both times the Lg32 shut down before the process
was complete. 262k QSOs.
73?? Vytas?? LZ2VQ
|
Temporarily rename Logger32.ini to Logger32.OLD. Run Logger32. What you see in Cherry-picking event viewer now ?
On 2024-12-02 月 17:00:20, Vytas VQ via groups.io <v.kudelis@...> wrote:
After reverting to v.329, the font size in the Cherry-picking
event viewer did not change.
73?? Vytas?? LZ2VQ
2024-12-02 09:47, ja1nlx via groups.io
ra??:
Vytas
Rollback to 4.0.329.
If it works then update to 4.0.330 again.
On 2024-12-02 月
16:40:43, Vytas VQ via groups.io
<v.kudelis@...> wrote:
After running it for the third time, the statistics
recalculation was successful with a few stops. I didn't
understand the essence of the error, I reviewed the data
of the specified QSO, as if everything was in order.
I noticed that Cherry-picking event viewer writes in
very large letters. I do not know how to reduce them.
73?? Vytas?? LZ2VQ
2024-12-01 15:46, Vytas VQ
via groups.io ra??:
I've already run the statistics recalculation twice
and both times the Lg32 shut down before the process
was complete. 262k QSOs.
73?? Vytas?? LZ2VQ
|
In that case, fine. Which parameter in the .ini file specifies
the font size for this window?
Thanks!
73?? Vytas?? LZ2VQ
2024-12-02 10:44, ja1nlx via groups.io
ra??:
toggle quoted message
Show quoted text
Temporarily rename Logger32.ini to Logger32.OLD.
Run Logger32.
What you see in Cherry-picking event viewer now ?
On 2024-12-02 月
17:00:20, Vytas VQ via groups.io
<v.kudelis@...> wrote:
After reverting to v.329, the font size in the
Cherry-picking event viewer did not change.
73?? Vytas?? LZ2VQ
2024-12-02 09:47, ja1nlx via
groups.io ra??:
Vytas
Rollback to 4.0.329.
If it works then update to 4.0.330 again.
On
2024-12-02 月 16:40:43, Vytas VQ via groups.io <v.kudelis@...>
wrote:
After running it for the third time, the
statistics recalculation was successful with a
few stops. I didn't understand the essence of
the error, I reviewed the data of the
specified QSO, as if everything was in order.
I noticed that Cherry-picking event viewer
writes in very large letters. I do not know
how to reduce them.
73?? Vytas?? LZ2VQ
2024-12-01 15:46,
Vytas VQ via groups.io ra??:
I've already run the statistics
recalculation twice and both times the Lg32
shut down before the process was complete.
262k QSOs.
73?? Vytas?? LZ2VQ
|
Vytas Next step. Delete Logger32.ini. Rename Logger32.OLD to Logger32.ini. Run Logger32. Rollback to the older version like 328, 327,,,, step-by-step.
On 2024-12-02 月 20:28:58, Vytas VQ via groups.io <v.kudelis@...> wrote:
In that case, fine. Which parameter in the .ini file specifies
the font size for this window?
Thanks!
73?? Vytas?? LZ2VQ
2024-12-02 10:44, ja1nlx via groups.io
ra??:
Temporarily rename Logger32.ini to Logger32.OLD.
Run Logger32.
What you see in Cherry-picking event viewer now ?
On 2024-12-02 月
17:00:20, Vytas VQ via groups.io
<v.kudelis@...> wrote:
After reverting to v.329, the font size in the
Cherry-picking event viewer did not change.
73?? Vytas?? LZ2VQ
2024-12-02 09:47, ja1nlx via
groups.io ra??:
Vytas
Rollback to 4.0.329.
If it works then update to 4.0.330 again.
On
2024-12-02 月 16:40:43, Vytas VQ via groups.io <v.kudelis@...>
wrote:
After running it for the third time, the
statistics recalculation was successful with a
few stops. I didn't understand the essence of
the error, I reviewed the data of the
specified QSO, as if everything was in order.
I noticed that Cherry-picking event viewer
writes in very large letters. I do not know
how to reduce them.
73?? Vytas?? LZ2VQ
2024-12-01 15:46,
Vytas VQ via groups.io ra??:
I've already run the statistics
recalculation twice and both times the Lg32
shut down before the process was complete.
262k QSOs.
73?? Vytas?? LZ2VQ
|
I went back to v.327, the same thing.
However, I found a problem. This happens after changing the PC
region setting from Lithuania to USA. I did this in v.330. When I
went back to the Lithuania setting, the letters are normal. But
then the DXpeditions 12.txt file is not created.
73?? Vytas?? LZ2VQ,? LY3BG
2024-12-02 13:37, ja1nlx via groups.io
ra??:
toggle quoted message
Show quoted text
Vytas
Next step.
Delete Logger32.ini.
Rename Logger32.OLD to Logger32.ini.
Run Logger32.
Rollback to the older version like 328, 327,,,,
step-by-step.
On 2024-12-02 月
20:28:58, Vytas VQ via groups.io
<v.kudelis@...> wrote:
In that case, fine. Which parameter in the .ini file
specifies the font size for this window?
Thanks!
73?? Vytas?? LZ2VQ
2024-12-02 10:44, ja1nlx via
groups.io ra??:
Temporarily rename Logger32.ini to
Logger32.OLD.
Run Logger32.
What you see in Cherry-picking event viewer now ?
On
2024-12-02 月 17:00:20, Vytas VQ via groups.io <v.kudelis@...>
wrote:
After reverting to v.329, the font size in
the Cherry-picking event viewer did not
change.
73?? Vytas?? LZ2VQ
2024-12-02 09:47,
ja1nlx via groups.io ra??:
Vytas
Rollback to 4.0.329.
If it works then update to 4.0.330
again.
On 2024-12-02 月 16:40:43,
Vytas VQ via groups.io <v.kudelis@...>
wrote:
After running it for the third
time, the statistics recalculation
was successful with a few stops. I
didn't understand the essence of the
error, I reviewed the data of the
specified QSO, as if everything was
in order.
I noticed that Cherry-picking event
viewer writes in very large letters.
I do not know how to reduce them.
73?? Vytas?? LZ2VQ
2024-12-01
15:46, Vytas VQ via groups.io ra??:
I've already run the statistics
recalculation twice and both times
the Lg32 shut down before the
process was complete. 262k QSOs.
73?? Vytas?? LZ2VQ
|
Vytas I do not know whether your strange character in Cherry-picking event viewer and other problem have same cause or not. Please wait for next auto update or use older version which works.
On 2024-12-02 月 20:51:40, Vytas VQ via groups.io <v.kudelis@...> wrote:
I went back to v.327, the same thing.
However, I found a problem. This happens after changing the PC
region setting from Lithuania to USA. I did this in v.330. When I
went back to the Lithuania setting, the letters are normal. But
then the DXpeditions 12.txt file is not created.
73?? Vytas?? LZ2VQ,? LY3BG
2024-12-02 13:37, ja1nlx via groups.io
ra??:
Vytas
Next step.
Delete Logger32.ini.
Rename Logger32.OLD to Logger32.ini.
Run Logger32.
Rollback to the older version like 328, 327,,,,
step-by-step.
On 2024-12-02 月
20:28:58, Vytas VQ via groups.io
<v.kudelis@...> wrote:
In that case, fine. Which parameter in the .ini file
specifies the font size for this window?
Thanks!
73?? Vytas?? LZ2VQ
2024-12-02 10:44, ja1nlx via
groups.io ra??:
Temporarily rename Logger32.ini to
Logger32.OLD.
Run Logger32.
What you see in Cherry-picking event viewer now ?
On
2024-12-02 月 17:00:20, Vytas VQ via groups.io <v.kudelis@...>
wrote:
After reverting to v.329, the font size in
the Cherry-picking event viewer did not
change.
73?? Vytas?? LZ2VQ
2024-12-02 09:47,
ja1nlx via groups.io ra??:
Vytas
Rollback to 4.0.329.
If it works then update to 4.0.330
again.
On 2024-12-02 月 16:40:43,
Vytas VQ via groups.io <v.kudelis@...>
wrote:
After running it for the third
time, the statistics recalculation
was successful with a few stops. I
didn't understand the essence of the
error, I reviewed the data of the
specified QSO, as if everything was
in order.
I noticed that Cherry-picking event
viewer writes in very large letters.
I do not know how to reduce them.
73?? Vytas?? LZ2VQ
2024-12-01
15:46, Vytas VQ via groups.io ra??:
I've already run the statistics
recalculation twice and both times
the Lg32 shut down before the
process was complete. 262k QSOs.
73?? Vytas?? LZ2VQ
|
The error message is not related to the ongoing recalculation of statistics. The error occurs when Logger32 is trying to send a 'keep alive' message to your
Telent socket. Fix that first.
?
To adjust the cherry-picker event viewer font size click on the CONFIG menu then click the FONT/SIZE button.
?
What else?
SeventyThree(s).
On 12/02/2024 2:40 AM EST Vytas VQ via groups.io <v.kudelis@...> wrote:
?
?
After running it for the third time, the statistics recalculation was successful with a few stops. I didn't understand the essence of the error, I reviewed the data of the specified QSO, as if everything was in order.
I noticed that Cherry-picking event viewer writes in very large letters. I do not know how to reduce them.
?
73?? Vytas?? LZ2VQ
?
?
2024-12-01 15:46, Vytas VQ via groups.io ra??:
I've already run the statistics recalculation twice and both times the Lg32 shut down before the process was complete. 262k QSOs.
?
73?? Vytas?? LZ2VQ
|
OK, thanks!
I didn't notice the FONT/SIZE button, my oversight, sorry...
73?? Vytas?? LZ2VQ
2024-12-02 15:14, Bob via groups.io ra??:
toggle quoted message
Show quoted text
To adjust the cherry-picker event viewer font size click on the CONFIG menu then click the FONT/SIZE button.
|
ZL2iFB
Stefano Zoli