Date   

Re: Helpfile

Sante - IK0HBN
 

Tony,
you must delete the file .chi.
73's Sante


At 18:50 05/03/2020, you wrote:
When I put the file in the L32 directory, I get this error. Then L32 hangs and I have to launch Task Mgr and Shut L32 down.
73
Tony
K2NV


[]

On Mar 5, 2020, at 12:43 PM, Anthony Buscaglia via Groups.Io <tonybb@... > wrote:

I downloaded an updated help file. Logger32.chm

I tried copying it to the Logger32 directory, but I can’t get it to come up in Logger32.

What’s the procedure?

Also is it normal for Windows UAC to come up every time I launch L32 on Win10?

73
TOny
K2NV






Re: Helpfile

Anthony Buscaglia
 

When I put the file in the L32 directory, I get this error. Then L32 hangs and I have to launch Task Mgr and Shut L32 down.
73
Tony
K2NV




On Mar 5, 2020, at 12:43 PM, Anthony Buscaglia via Groups.Io <tonybb@...> wrote:

I downloaded an updated help file. Logger32.chm

I tried copying it to the Logger32 directory, but I can’t get it to come up in Logger32.

What’s the procedure?

Also is it normal for Windows UAC to come up every time I launch L32 on Win10?

73
TOny
K2NV







Helpfile

Anthony Buscaglia
 

I downloaded an updated help file. Logger32.chm

I tried copying it to the Logger32 directory, but I can’t get it to come up in Logger32.

What’s the procedure?

Also is it normal for Windows UAC to come up every time I launch L32 on Win10?

73
TOny
K2NV


Unable to open L32 and more

kenfilmer@outlook.com
 

I’ve happily used L32 for years until the last auto update came along this week. Once I updated I was unable open Logger32. I tried everything, no success so I reloaded the programme, set up bands and modes etc!

Loading my saved log ADIF L32 wouldn’t load some 5000 contacts and L32 said recalculate statistics, which I did.. Now whenever I log a contact despite the last QSO being numbered 28000, the next QSO number is number 1.

Has anybody any ideas what went wrong?

Ken G3XPO

 

Sent from Mail for Windows 10

 


Re: Where is this label...?

rick@...
 

Thanks a lot, Dan!
Rick


Re: Where is this label...?

Dan Atchison
 

Right-click in the Entry callsign window, select Control-F

On 3/4/2020 10:49 AM, rick@... wrote:
I used to have a nice label pop up with the callsign I was working. I used to place it on the map. It disappeared suddenly. How do I get it back?
Rick, OZ5RM


Where is this label...?

rick@...
 

I used to have a nice label pop up with the callsign I was working. I used to place it on the map. It disappeared suddenly. How do I get it back?
Rick, OZ5RM


Re: Error Message

Bob Schofield
 

Thanks

I found the problem this morning.  Somehow a menu setting at menu 19 on the FT857 changed.  I had not changed any menus but for some unknown reason it changed from CAT to Tune.

All is back to normal operations today.

Bob/VE1RSM


Re: Error Message

ja1nlx
 

Bob

What is your settings in wsjtx Radio TAB ?  PTT by ?  Split ?

What is your Radio ?

Logger32 does not use Hamlib. The message come from wsjtx.

I always use jtdx and sometimes use wsjtx for testing. Only things I notice is that

the latest Hamlib looks not working properly with ICOM radio.

73


On 2020/03/04 9:20, Bob Schofield wrote:
Group (I've also posted this on the FT8 site)

I have been using WSJT-X with both N1MM and Logger32 for some time now with no problems.

This past weekend I dismantled my setup and used it at a club setting, through a dummy load to demonstrate Digital Contesting using: N1MM, MMVARI and WSJT-X.

Today I put the station back to regular use in my radio room.

Problem when trying to use it with Logger32 is showing up.  Note: working just fine with N1MM.

Hamlib error: Command rejected by the rig while setting frequency.

I keep getting the above error message whenever I either use the Tune or TX buttons.  When the TX stops, the above error message shows up.

To the best of my knowledge the only thing that changed was when I opened Logger32 today it updated to the latest version.  I thought maybe this was causing the problem so I went in and did a roll back to the previous version, and the message still pots up.

I have gone through all the setting in Logger32 and they are good.  I also went through all the setting in WSJT-X and all were set as to the way there were before, no changes.

From what I can see while using WSJT-X to control the radio, it changes bands and modes with not problem and the radio responds to the changes.

When I TX it sends the message, no problem.  Only when TX stops does this message appear.

Any suggestions as to why this message keeps popping up?

Bob/VE1RSM
--
73 de aki
JA1NLX


Re: Error Message

Gary Hinson
 

Hi Bob.

 

It sounds to me as if the problem lies in the communications between WSJT-X and your radio, using the Hamlib functions to set the radio into split mode and QSY the TX VFO.

 

Under the radio tab in F2 settings, try changing “Split Operation” from “Rig”  to “Fake it” or “None” to skip the radio commands: if tune works now, that’s homed-in on the problem.

 

However, this is the support forum for Logger32, which I don’t think has any involvement in your problem.  Try the WSJT-X support forum instead.

 

Or, for kicks, try JTDX instead of WSJT-X to see if that magically clears the problem.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob Schofield
Sent: 04 March 2020 13:20
To: hamlogger@groups.io
Subject: [hamlogger] Error Message

 

Group (I've also posted this on the FT8 site)

I have been using WSJT-X with both N1MM and Logger32 for some time now with no problems.

This past weekend I dismantled my setup and used it at a club setting, through a dummy load to demonstrate Digital Contesting using: N1MM, MMVARI and WSJT-X.

Today I put the station back to regular use in my radio room.

Problem when trying to use it with Logger32 is showing up.  Note: working just fine with N1MM.

Hamlib error: Command rejected by the rig while setting frequency.

I keep getting the above error message whenever I either use the Tune or TX buttons.  When the TX stops, the above error message shows up.

To the best of my knowledge the only thing that changed was when I opened Logger32 today it updated to the latest version.  I thought maybe this was causing the problem so I went in and did a roll back to the previous version, and the message still pots up.

I have gone through all the setting in Logger32 and they are good.  I also went through all the setting in WSJT-X and all were set as to the way there were before, no changes.

From what I can see while using WSJT-X to control the radio, it changes bands and modes with not problem and the radio responds to the changes.

When I TX it sends the message, no problem.  Only when TX stops does this message appear.

Any suggestions as to why this message keeps popping up?

Bob/VE1RSM


Error Message

Bob Schofield
 

Group (I've also posted this on the FT8 site)

I have been using WSJT-X with both N1MM and Logger32 for some time now with no problems.

This past weekend I dismantled my setup and used it at a club setting, through a dummy load to demonstrate Digital Contesting using: N1MM, MMVARI and WSJT-X.

Today I put the station back to regular use in my radio room.

Problem when trying to use it with Logger32 is showing up.  Note: working just fine with N1MM.

Hamlib error: Command rejected by the rig while setting frequency.

I keep getting the above error message whenever I either use the Tune or TX buttons.  When the TX stops, the above error message shows up.

To the best of my knowledge the only thing that changed was when I opened Logger32 today it updated to the latest version.  I thought maybe this was causing the problem so I went in and did a roll back to the previous version, and the message still pots up.

I have gone through all the setting in Logger32 and they are good.  I also went through all the setting in WSJT-X and all were set as to the way there were before, no changes.

From what I can see while using WSJT-X to control the radio, it changes bands and modes with not problem and the radio responds to the changes.

When I TX it sends the message, no problem.  Only when TX stops does this message appear.

Any suggestions as to why this message keeps popping up?

Bob/VE1RSM


Re: Name Field Automatically Filled in?

Peter Sidler - HB9PJT
 

Hi Aki

Thank you very much for your help. Just what I was looking for. It's always amazing what Bob has built into Logger32.

73, Peter - HB9PJT


Re: Name Field Automatically Filled in?

ja1nlx
 

Peter

Right click on Logbook Entry Window.
Click Setup.
Click Setup QSO Mask
Check Name box upper and/or lower then click Apply. 

73

On 2020/03/03 18:03, Peter Sidler - HB9PJT via Groups.Io wrote:
Is there a way to configure Logger32 to automatically fill the name field in the new QSO with the name of the last QSO from the same callsign? Thanks for helping.

73, Peter - HB9PJT
--
73 de aki
JA1NLX


Name Field Automatically Filled in?

Peter Sidler - HB9PJT
 

Is there a way to configure Logger32 to automatically fill the name field in the new QSO with the name of the last QSO from the same callsign? Thanks for helping.

73, Peter - HB9PJT


Re: FT8 spots in DX Spot Window

john Kalou
 

Good morning  how to disable the command: SET/SKIMMER after to enable the cluster ?

73   sv9rgi  Giannis 


Re: Can't edit contacts in the logbook

Ken McVie <kenmc@...>
 

That's interesting Aki!!
I'll keep an eye on it when another update comes along to see if that changes anything.

73
Ken ZL4NR

On 2/03/2020 4:01 pm, ja1nlx wrote:

Ken

I am glad to hear that.

I made testing with  "Auto golist lookup" checked and do not see your problem....
Maybe something different between our settings.

73


On 2020/03/02 10:31, Ken McVie wrote:
Aki, I think I found the problem!!

As you probably saw, Jim Altman sent me a link for a program to compare two files, so I downloaded this & entered the two files. It found a few differences in the whole INI file, mostly to do with window positions. But one difference was that the OLD INI file had the Golist auto lookup checked, & the earlier version didn't.
I then opened L32, & checked the auto lookup for Golist, & the program went back to not being able to edit anything in the logbook page. I then unchecked the auto lookup of Golist, & I can edit anything in the logbook page again!! So there is a tie up between the Golist lookup being on or off that is causing this problem.

Once again, many thanks to Aki, & Jim for the help.

73
Ken ZL4NR



On 2/03/2020 11:49 am, ja1nlx wrote:

Ken

As you say it may be better for you to copy/paste older Logger32.ini on current one.

73

On 2020/03/02 7:24, Ken McVie wrote:
JA1NLX,
Sorry for the delay in replying, life got in the way!!!!

I have 63 lines in that section of the INI file, do you mean to delete them all??  If I do this, will it mean I have to reset all those parameters??  I could print out a copy I guess, which would make it easier to "remake" the list bit by bit, testing as I go to see where the problem lies.

In the 'UPDATE' files of L32, I have a INI file dated early February, could I exchange this for my current one & see what happens??

I tried changing the Page Index & the Page Index Column numbers to what you sent me, & that didn't make any difference.

73
Ken ZL4NR


On 28/02/2020 10:09 pm, ja1nlx wrote:

Ken

Delete Logger32.ini.

Rename Logger32.ini.OLD to Logger32.ini again.

Open Logger32.ini with text editor.

Maybe something wrong in [wndLogbookPage Settings] section.

Delete all lines in this section. Run Logger32. How now ?

[wndLogbookPage Settings]
Logbook Page Index= 0
Logbook Page Index Column= 3

73

On 2020/02/28 17:59, Ken McVie wrote:
That works ok. Now how do I find the difference in the two INI files??

73
Ken

On 28/02/2020 9:53 pm, ja1nlx wrote:

Ken

Try with virgin Logger32.ini.

Look for Logger32.ini in the Logger32 folder. Rename it Logger32.ini.OLD.

Run Logger32. Try edit in Logbook page window. How now ?

73

On 2020/02/28 17:44, Ken McVie wrote:
I should add that I have done this lots in the past without trouble.

73
Ken ZL4NR

On 28/02/2020 9:38 pm, ja1nlx wrote:

Ken

What you see when you click any line. I see the line highlighted with Yellow back color.
This color depends on your setting.


73


On 2020/02/28 16:18, Ken McVie wrote:
Using version 3.50.408 on W10 Home desktop computer.

I used to be able to click on a [for instance] name in the logbook alongside a callsign, & change it for something else. Now I can't change anything on a QSO line by clicking on it.

I have a QSO with Rarotonga which shows the IOTA number as OC-124 -- it should be OC- 013 according to the QSL card that I have received, & I can't find a way of changing this.

Is anybody else seeing this behaviour of not being able to edit a line in the logbook??

Any thoughts much appreciated.

73
Ken ZL4NR



--
73 de aki
JA1NLX

--
73 de aki
JA1NLX

--
73 de aki
JA1NLX

--
73 de aki
JA1NLX

--
73 de aki
JA1NLX


Re: Can't edit contacts in the logbook

ja1nlx
 

Ken

I am glad to hear that.

I made testing with  "Auto golist lookup" checked and do not see your problem....
Maybe something different between our settings.

73


On 2020/03/02 10:31, Ken McVie wrote:
Aki, I think I found the problem!!

As you probably saw, Jim Altman sent me a link for a program to compare two files, so I downloaded this & entered the two files. It found a few differences in the whole INI file, mostly to do with window positions. But one difference was that the OLD INI file had the Golist auto lookup checked, & the earlier version didn't.
I then opened L32, & checked the auto lookup for Golist, & the program went back to not being able to edit anything in the logbook page. I then unchecked the auto lookup of Golist, & I can edit anything in the logbook page again!! So there is a tie up between the Golist lookup being on or off that is causing this problem.

Once again, many thanks to Aki, & Jim for the help.

73
Ken ZL4NR



On 2/03/2020 11:49 am, ja1nlx wrote:

Ken

As you say it may be better for you to copy/paste older Logger32.ini on current one.

73

On 2020/03/02 7:24, Ken McVie wrote:
JA1NLX,
Sorry for the delay in replying, life got in the way!!!!

I have 63 lines in that section of the INI file, do you mean to delete them all??  If I do this, will it mean I have to reset all those parameters??  I could print out a copy I guess, which would make it easier to "remake" the list bit by bit, testing as I go to see where the problem lies.

In the 'UPDATE' files of L32, I have a INI file dated early February, could I exchange this for my current one & see what happens??

I tried changing the Page Index & the Page Index Column numbers to what you sent me, & that didn't make any difference.

73
Ken ZL4NR


On 28/02/2020 10:09 pm, ja1nlx wrote:

Ken

Delete Logger32.ini.

Rename Logger32.ini.OLD to Logger32.ini again.

Open Logger32.ini with text editor.

Maybe something wrong in [wndLogbookPage Settings] section.

Delete all lines in this section. Run Logger32. How now ?

[wndLogbookPage Settings]
Logbook Page Index= 0
Logbook Page Index Column= 3

73

On 2020/02/28 17:59, Ken McVie wrote:
That works ok. Now how do I find the difference in the two INI files??

73
Ken

On 28/02/2020 9:53 pm, ja1nlx wrote:

Ken

Try with virgin Logger32.ini.

Look for Logger32.ini in the Logger32 folder. Rename it Logger32.ini.OLD.

Run Logger32. Try edit in Logbook page window. How now ?

73

On 2020/02/28 17:44, Ken McVie wrote:
I should add that I have done this lots in the past without trouble.

73
Ken ZL4NR

On 28/02/2020 9:38 pm, ja1nlx wrote:

Ken

What you see when you click any line. I see the line highlighted with Yellow back color.
This color depends on your setting.


73


On 2020/02/28 16:18, Ken McVie wrote:
Using version 3.50.408 on W10 Home desktop computer.

I used to be able to click on a [for instance] name in the logbook alongside a callsign, & change it for something else. Now I can't change anything on a QSO line by clicking on it.

I have a QSO with Rarotonga which shows the IOTA number as OC-124 -- it should be OC- 013 according to the QSL card that I have received, & I can't find a way of changing this.

Is anybody else seeing this behaviour of not being able to edit a line in the logbook??

Any thoughts much appreciated.

73
Ken ZL4NR



--
73 de aki
JA1NLX

--
73 de aki
JA1NLX

--
73 de aki
JA1NLX

--
73 de aki
JA1NLX

--
73 de aki
JA1NLX


Re: Can't edit contacts in the logbook

Ken McVie <kenmc@...>
 

Aki, I think I found the problem!!

As you probably saw, Jim Altman sent me a link for a program to compare two files, so I downloaded this & entered the two files. It found a few differences in the whole INI file, mostly to do with window positions. But one difference was that the OLD INI file had the Golist auto lookup checked, & the earlier version didn't.
I then opened L32, & checked the auto lookup for Golist, & the program went back to not being able to edit anything in the logbook page. I then unchecked the auto lookup of Golist, & I can edit anything in the logbook page again!! So there is a tie up between the Golist lookup being on or off that is causing this problem.

Once again, many thanks to Aki, & Jim for the help.

73
Ken ZL4NR



On 2/03/2020 11:49 am, ja1nlx wrote:

Ken

As you say it may be better for you to copy/paste older Logger32.ini on current one.

73

On 2020/03/02 7:24, Ken McVie wrote:
JA1NLX,
Sorry for the delay in replying, life got in the way!!!!

I have 63 lines in that section of the INI file, do you mean to delete them all??  If I do this, will it mean I have to reset all those parameters??  I could print out a copy I guess, which would make it easier to "remake" the list bit by bit, testing as I go to see where the problem lies.

In the 'UPDATE' files of L32, I have a INI file dated early February, could I exchange this for my current one & see what happens??

I tried changing the Page Index & the Page Index Column numbers to what you sent me, & that didn't make any difference.

73
Ken ZL4NR


On 28/02/2020 10:09 pm, ja1nlx wrote:

Ken

Delete Logger32.ini.

Rename Logger32.ini.OLD to Logger32.ini again.

Open Logger32.ini with text editor.

Maybe something wrong in [wndLogbookPage Settings] section.

Delete all lines in this section. Run Logger32. How now ?

[wndLogbookPage Settings]
Logbook Page Index= 0
Logbook Page Index Column= 3

73

On 2020/02/28 17:59, Ken McVie wrote:
That works ok. Now how do I find the difference in the two INI files??

73
Ken

On 28/02/2020 9:53 pm, ja1nlx wrote:

Ken

Try with virgin Logger32.ini.

Look for Logger32.ini in the Logger32 folder. Rename it Logger32.ini.OLD.

Run Logger32. Try edit in Logbook page window. How now ?

73

On 2020/02/28 17:44, Ken McVie wrote:
I should add that I have done this lots in the past without trouble.

73
Ken ZL4NR

On 28/02/2020 9:38 pm, ja1nlx wrote:

Ken

What you see when you click any line. I see the line highlighted with Yellow back color.
This color depends on your setting.


73


On 2020/02/28 16:18, Ken McVie wrote:
Using version 3.50.408 on W10 Home desktop computer.

I used to be able to click on a [for instance] name in the logbook alongside a callsign, & change it for something else. Now I can't change anything on a QSO line by clicking on it.

I have a QSO with Rarotonga which shows the IOTA number as OC-124 -- it should be OC- 013 according to the QSL card that I have received, & I can't find a way of changing this.

Is anybody else seeing this behaviour of not being able to edit a line in the logbook??

Any thoughts much appreciated.

73
Ken ZL4NR



--
73 de aki
JA1NLX

--
73 de aki
JA1NLX

--
73 de aki
JA1NLX

--
73 de aki
JA1NLX


Re: Can't edit contacts in the logbook

Ken McVie <kenmc@...>
 

Thanks Jim, I'll give that a try.

73
Ken ZL4NR

On 2/03/2020 1:47 pm, Jim Altman wrote:

Google WinMerge.  Its free and will compare two files line by line allowing movement from one file to the other.

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Ken McVie
Sent: Sunday, March 1, 2020 7:45 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Can't edit contacts in the logbook

 

JA1NLX

I renamed my L32 INI file to OLD, & then copied & pasted the earlier edition into the L32 folder. Opened L32, & all seems to be working again!!
So I then opened both INI files in Notepad, & went thru each line [63 of them] to compare [visually] & I can't see any difference!! Is there a program for comparing files that might show where the fault lies??
Many thanks for the help Aki, appreciated.

73
Ken ZL4NR

On 2/03/2020 11:49 am, ja1nlx wrote:

Ken

As you say it may be better for you to copy/paste older Logger32.ini on current one.

73

On 2020/03/02 7:24, Ken McVie wrote:

JA1NLX,
Sorry for the delay in replying, life got in the way!!!!

I have 63 lines in that section of the INI file, do you mean to delete them all??  If I do this, will it mean I have to reset all those parameters??  I could print out a copy I guess, which would make it easier to "remake" the list bit by bit, testing as I go to see where the problem lies.

In the 'UPDATE' files of L32, I have a INI file dated early February, could I exchange this for my current one & see what happens??

I tried changing the Page Index & the Page Index Column numbers to what you sent me, & that didn't make any difference.

73
Ken ZL4NR

On 28/02/2020 10:09 pm, ja1nlx wrote:

Ken

Delete Logger32.ini.

Rename Logger32.ini.OLD to Logger32.ini again.

Open Logger32.ini with text editor.

Maybe something wrong in [wndLogbookPage Settings] section.

Delete all lines in this section. Run Logger32. How now ?

[wndLogbookPage Settings]
Logbook Page Index= 0
Logbook Page Index Column= 3

73

On 2020/02/28 17:59, Ken McVie wrote:

That works ok. Now how do I find the difference in the two INI files??

73
Ken

On 28/02/2020 9:53 pm, ja1nlx wrote:

Ken

Try with virgin Logger32.ini.

Look for Logger32.ini in the Logger32 folder. Rename it Logger32.ini.OLD.

Run Logger32. Try edit in Logbook page window. How now ?

73

On 2020/02/28 17:44, Ken McVie wrote:

I should add that I have done this lots in the past without trouble.

73
Ken ZL4NR

On 28/02/2020 9:38 pm, ja1nlx wrote:

Ken

What you see when you click any line. I see the line highlighted with Yellow back color.
This color depends on your setting.

 

73

 

On 2020/02/28 16:18, Ken McVie wrote:

Using version 3.50.408 on W10 Home desktop computer.

I used to be able to click on a [for instance] name in the logbook alongside a callsign, & change it for something else. Now I can't change anything on a QSO line by clicking on it.

I have a QSO with Rarotonga which shows the IOTA number as OC-124 -- it should be OC- 013 according to the QSL card that I have received, & I can't find a way of changing this.

Is anybody else seeing this behaviour of not being able to edit a line in the logbook??

Any thoughts much appreciated.

73
Ken ZL4NR


--
73 de aki
JA1NLX

 

--
73 de aki
JA1NLX

 

--
73 de aki
JA1NLX

 

--
73 de aki
JA1NLX

 



Re: Can't edit contacts in the logbook

Jim Altman
 

Google WinMerge.  Its free and will compare two files line by line allowing movement from one file to the other.

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Ken McVie
Sent: Sunday, March 1, 2020 7:45 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Can't edit contacts in the logbook

 

JA1NLX

I renamed my L32 INI file to OLD, & then copied & pasted the earlier edition into the L32 folder. Opened L32, & all seems to be working again!!
So I then opened both INI files in Notepad, & went thru each line [63 of them] to compare [visually] & I can't see any difference!! Is there a program for comparing files that might show where the fault lies??
Many thanks for the help Aki, appreciated.

73
Ken ZL4NR

On 2/03/2020 11:49 am, ja1nlx wrote:

Ken

As you say it may be better for you to copy/paste older Logger32.ini on current one.

73

On 2020/03/02 7:24, Ken McVie wrote:

JA1NLX,
Sorry for the delay in replying, life got in the way!!!!

I have 63 lines in that section of the INI file, do you mean to delete them all??  If I do this, will it mean I have to reset all those parameters??  I could print out a copy I guess, which would make it easier to "remake" the list bit by bit, testing as I go to see where the problem lies.

In the 'UPDATE' files of L32, I have a INI file dated early February, could I exchange this for my current one & see what happens??

I tried changing the Page Index & the Page Index Column numbers to what you sent me, & that didn't make any difference.

73
Ken ZL4NR

On 28/02/2020 10:09 pm, ja1nlx wrote:

Ken

Delete Logger32.ini.

Rename Logger32.ini.OLD to Logger32.ini again.

Open Logger32.ini with text editor.

Maybe something wrong in [wndLogbookPage Settings] section.

Delete all lines in this section. Run Logger32. How now ?

[wndLogbookPage Settings]
Logbook Page Index= 0
Logbook Page Index Column= 3

73

On 2020/02/28 17:59, Ken McVie wrote:

That works ok. Now how do I find the difference in the two INI files??

73
Ken

On 28/02/2020 9:53 pm, ja1nlx wrote:

Ken

Try with virgin Logger32.ini.

Look for Logger32.ini in the Logger32 folder. Rename it Logger32.ini.OLD.

Run Logger32. Try edit in Logbook page window. How now ?

73

On 2020/02/28 17:44, Ken McVie wrote:

I should add that I have done this lots in the past without trouble.

73
Ken ZL4NR

On 28/02/2020 9:38 pm, ja1nlx wrote:

Ken

What you see when you click any line. I see the line highlighted with Yellow back color.
This color depends on your setting.

 

73

 

On 2020/02/28 16:18, Ken McVie wrote:

Using version 3.50.408 on W10 Home desktop computer.

I used to be able to click on a [for instance] name in the logbook alongside a callsign, & change it for something else. Now I can't change anything on a QSO line by clicking on it.

I have a QSO with Rarotonga which shows the IOTA number as OC-124 -- it should be OC- 013 according to the QSL card that I have received, & I can't find a way of changing this.

Is anybody else seeing this behaviour of not being able to edit a line in the logbook??

Any thoughts much appreciated.

73
Ken ZL4NR


--
73 de aki
JA1NLX

 

--
73 de aki
JA1NLX

 

--
73 de aki
JA1NLX

 

--
73 de aki
JA1NLX

 

4501 - 4520 of 83551