Log4OM

IW3HMH wrote:

G4POP wrote: Next release of Log4om allows you to identify the actual file name, not just the path to Logbook.adi

If i remember correctly this feature is already implemented. If users has only the path (as previous version requires) i will automatically add "logbook.adi" for backward compatibility, but now you can (must, in the new release) select the ADIF file complete with his name

Yes you have added it to the Alpha that you are working on but it has not been released to the public yet

G4POP wrote:

N9BBE wrote:Have another issue. I have Log4OM and FLDigi working together as far as reading the radio info but Log4 is not logging contacts made in FLDigi. The contacts are getting into the FLDigi log. Probably another oversite again on my part.

I know what the issue is, FLDigi is not using the default logbook named "Logbook" it is using one called "Newlog" as a result Log4om cannot find the ADIF.

Problem is that I will need to talk you through the fix on Skype, is that possible?

Next release of Log4om allows you to identify the actual file name, not just the path to Logbook.adi

Terry, I could meet you on skype over the weekend. Before then I'm thinking I could make a copy of my fldigi log and name it "Newlog". Point FLDigi to the new file and both should be happy.

Thats the problem with the version that you have you cannot select the actual file 'Newlog' as Log4OM had 'Logbook.adi' hard coded and only allows you to select the path

Yes I understand now that I am in front of the computer at home. I have FLDigi setup to use "logbook.adi". I verified that by saving a QSO in FLDigi and checking the date and time stamp on the logbook.adi file. Also when I open the FLDigi logbook in FLDigi the file it's openning is "logbook.adi" according to the title bar across the top of the FLDigi logbook window. The FLDigi logbook file is located in 'C:\Users\Dad\fldigi.files\logs'. The ADIF File Polling in the Communicator Settings is exactly the same, 'C:\Users\Dad\fldigi.files\logs\logbook.adi'.

N9BBE wrote:Yes I understand now that I am in front of the computer at home. I have FLDigi setup to use "logbook.adi". I verified that by saving a QSO in FLDigi and checking the date and time stamp on the logbook.adi file. Also when I open the FLDigi logbook in FLDigi the file it's openning is "logbook.adi" according to the title bar across the top of the FLDigi logbook window. The FLDigi logbook file is located in 'C:\Users\Dad\fldigi.files\logs'. The ADIF File Polling in the Communicator Settings is exactly the same, 'C:\Users\Dad\fldigi.files\logs\logbook.adi'.

This sounds correct and set up like that it should work fine, if it is not working there must be something else affecting it.

Could this wait until we can talk on Skype?