¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. Hamlogger
  2. Topics

Previous QSOs window

 

Bob,
I have an operator in my log that has been worked a lot. When logger32 looks up this callsign it looks like its totaling the QSOs up 3 different times.? Because the number appears and disappears two times then finally appears. Just figured i let you know since it seems like maybe there is some bug in the code causing it to fire off 3 times.
?
Joe
N3XLS
 

Thanks for the observation. I checked the code and Previous QSOs are displayed only once. Then, after that if there are more QSOs than visible rows on the form the caption of the form is modified to include the number of QSOs. That too is executed only once. Finally, the grid adjusts the top row visible so that the most recent QSO is on the last mine. This too is executed only once.
?
Reading the logbook, populating the grid, modifying the caption, adjusting the grid to show the last QSO at the bottom, is all done without taking a breather for the graphics to catch up. There should be little or no blinking or flashing of the window while the QSOs are loaded and displayed.
?
Maybe others have similar observations? SeventyThree(s).
?
?
?
?

On 03/22/2025 12:25 PM EDT Joe N3XLS via groups.io <n3xls@...> wrote:
?
?
Bob,
I have an operator in my log that has been worked a lot. When logger32 looks up this callsign it looks like its totaling the QSOs up 3 different times.? Because the number appears and disappears two times then finally appears. Just figured i let you know since it seems like maybe there is some bug in the code causing it to fire off 3 times.
?
Joe
N3XLS

 

I must be seeing the action that you describe. There is no blinking or flashing of the window as you say its only the number appearing and disappearing to finally appear after its done processing. Plus I only see it on the guys that have 1000+ previous.? The number never changes, its always the same. But with 180k+ that is a long haul of data to be counting up and be searching for all those QSOs.? I doubt logger32 was ever meant or thought of to be tallying large amounts of QSO's from the same operator in the thousands. So I'm probably an edge case here.?
?
I'm afraid to say my logbook is becoming one of those big data repositories. I might dwarf some of the other power users on this forum though. I think I remember someone here posted they had more than 300k+ QSOs in their logbook. So we are probably all the edge cases for the stuff that was never dreamed of getting that large. ?

 

Best I could find was 17 QSOs. My tests were not visual observations, I actually debugged the code, and it is only executed once. It is possible/probable that creating a large list of 1000+ QSOs an the fly, loading them into a grid, then adjusting the grid up 990 (or so) rows to show the last QSO, is a little taxing on the PC graphics causing the title bar on the form to repaint.
?
Keep an eye on the Logbook details window so you don't run out?of space. Also, you might consider rebuilding your logbook periodically to improve its performance. With a big log like that, First made an ADIF backup and hide it under the mattress. Then, before going to bed start the rebuild.
?
SeventyThree(s).

On 03/22/2025 1:41 PM EDT Joe N3XLS via groups.io <n3xls@...> wrote:
?
?
I must be seeing the action that you describe. There is no blinking or flashing of the window as you say its only the number appearing and disappearing to finally appear after its done processing. Plus I only see it on the guys that have 1000+ previous.? The number never changes, its always the same. But with 180k+ that is a long haul of data to be counting up and be searching for all those QSOs.? I doubt logger32 was ever meant or thought of to be tallying large amounts of QSO's from the same operator in the thousands. So I'm probably an edge case here.?
?
I'm afraid to say my logbook is becoming one of those big data repositories. I might dwarf some of the other power users on this forum though. I think I remember someone here posted they had more than 300k+ QSOs in their logbook. So we are probably all the edge cases for the stuff that was never dreamed of getting that large. ?

1 - 4 of 4