Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- Hamlogger
- Messages
Search
DX spot map, wrong country
Hi all,
?
Have you ever wondered why a spot icon is placed in the wrong country in the DX Spot map window?
This only occurs from Non-RBN sources.
Seems to happen a lot some times, then nothing for days etc.?
?
If a spot is sent to the cluster with a Locator (6 fig) in the comments then that locater appears to take precedence over the country location which is OK, unless the spot includes the locator of the sender and not the DX.?
?
Also happens when both locators are sent in the comments, perhaps it only take the 1st one?
?
Trivial I know, but may throw up other issues.
?
73, Tony G2NF.
? |
Re: Previous QSOs window
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).
|
Re: Previous QSOs window
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. ? |
Re: Previous QSOs window
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).
?
?
?
?
|
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 |
Re: Logger32 stops at the loading logbook entry window
The help file section also explains how to enable debugging when Logger32 starts, not just after it has started.
?
SeventyThree(s).
|
Re: Logger32 stops at the loading logbook entry window
sorry, was not clear... I went to the help file, but? to debug and view, the program needed to be running.
but Good new!
?
I updated? and reinstalled W10 and all works fine now... as I suspected, it was a? W10 problem
thanks much Bob for hanging? in? there with me!
? |
Re: Logger32 stops at the loading logbook entry window
I think I'm pissing into the wind. My last message included the URL of the help file (see the blue text below below).
?
You said? - I did? install on another computer and xfered all to this? PC - Xfered all what? Why transfer anything? EXACTLY what did you do?
?
SeventyThree(s).
?
?
... and, as a last resort, look at section 34.4 of the help file. As a reminder, that's at?
?
SeventyThree(s).
?
|
Re: Logger32 stops at the loading logbook entry window
Re? Help file... Logger needs to be running? to see that.. so unable to do it.
I did? install on another computer and xfered all to this? PC, but to no avail.
?
I feel like? must be a W10 problem, but am not going to reset? PC just for this program...
It's a shame, because I love this program...
W10 is often a bother, now especially.
?
thanks though for all your help,
Randy, KF4O |
Re: Logger32 stops at the loading logbook entry window
... and, as a last resort, look at section 34.4 of the help file. As a reminder, that's at
?
SeventyThree(s).
|
Re: Logger32 stops at the loading logbook entry window
Randy Try to install Logger32 on another PC if you have one. Try reset PC to factory default and install Logger32 (if possible) 73 de aki JA1NLX
|
Re: Logger32 stops at the loading logbook entry window
Oh well, I'm out of ideas. Do you have your logs stored away somewhere in ADIF format so that you can load/use a logging program that works on your PC? If not, do you have a zipped Logger32 backup that I could use to extract your logs for you? SeventyThree(s).
|
Re: Logger32 stops at the loading logbook entry window
... and, if you need assistance/guidance on how to recover your logbook, just holler. SeventyThree(s).
|
Re: Logger32 stops at the loading logbook entry window
I have no more ideas or suggestions. You might try running the Windows system file checker (Google it) to check the validity of the operating system on your PC. Good luck, SeventyThree(s).
|
Re: Logger32 stops at the loading logbook entry window
No, do not copy any files. That way you are certain you haven't simply copied the?cause of the problem to the new install.
?
What exactly do you see? Logger32 freezes forever, Logger32 simply disappears with a puff of smoke and the small of sulfur in the air? Have you tried setting Logger32 to run in compatibility mode?
?
SeventyThree(s).
?
|
to navigate to use esc to dismiss