开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育

entering grid


 

I apologize if this has been discussed here before.
We have a new toy called GOTA - Grids on the Air. You need to have the grid in the adif record. After manually inserting the grid into the existing QSO record (a QSO way back in time) the Logger thinks for a while, then uselessly opens the window to change the Administrative primary and secondary subdivision. Closing that window causes the jump to the end of the logbook. You have to search again for the original QSO. You see then that the grid was entered correctly , but you have lost few seconds of time. To process hundreds or thousands of logbook records this way drives you crazy. Could this bug be fixed please?
73, Ruda, OK2QA


 

A bug. or operator malfunction?
?
I assume (always dangerous) that in your Logbook Page Window the column to the right of GRIDSQUARE (or whateveryou have called it) column?is either STATE or CNTY (or whatever you have called them).
?
So, after you have edited/added the GRIDSQUARE if you type <TAB> the GRIDSQUARE will be added/edited then the cursor focus moves to the STATE/CNTY column, and the Change Admin Subdivision Window opens as expected. Try typing <ENTER> instead of <TAB>.
?
Only six days to go until April 1st. SeventyThree(s).

On 03/26/2025 5:58 AM EDT Rudolf Klvana via groups.io <ok2qa@...> wrote:
?
?
I apologize if this has been discussed here before.
We have a new toy called GOTA - Grids on the Air. You need to have the grid in the adif record. After manually inserting the grid into the existing QSO record (a QSO way back in time) the Logger thinks for a while, then uselessly opens the window to change the Administrative primary and secondary subdivision. Closing that window causes the jump to the end of the logbook. You have to search again for the original QSO. You see then that the grid was entered correctly , but you have lost few seconds of time. To process hundreds or thousands of logbook records this way drives you crazy. Could this bug be fixed please?
73, Ruda, OK2QA


 

(b) is correct - operator malfunction. Cause was exact as you have described. I am glad I could ask and get the immediate answer from the author of the software. It was not the first time I asked for help as I use the Logger since the 16 bit version. Thank you, Bob.