Log4OM

Seems like odd?? behavior -

Latest V in use: When double clicking a callsign in the cluster list the callsign field in the logbook does not initially populate with the cluster callsign until the callsign in the cluster field is selected a second time with a single click. However, the radio does change frequency and other cluster information seems to populate upon the initial double click on the callsign in the cluster field.

Potential problem to fix: Populate cluster callsign to logbook field upon initial double click

It appears that a callsign previously manually entered into the logbook remains there even after a double click on any callsign in the cluster list. The "old" callsign in the logbook will clear and update to match the cluster list selection after a second single click on the cluster. Even after shutting down the radio and restarting the next day (keeping LOG4OM active), the same previously manually searched "old" callsign remains populated in the logbook. Also, changing frequency on the radio always jumps back to the previously manually entered "old" callsign in the log.

Potential problem to fix: Clear previously manually entered callsign from continuing to auto populate logbook callsign field
 
Radio = IC-7760 w/Hamlib (7760 V Alpha) for CAT

Wade

1. Single click populates the call sign field for lookup


2. Double click activates above PLUS sends CAT commant to radio to change frequency and mode

I had a 7760 for some time and found Omnirig far better than the ponderous Hamlib so perhaps your 'Alpha' version is causing the issue?

Terry, if you had the new 7760 then you probably noticed that the Omnirig file for some reason defaults to filter 2 and yes the same old call sign still shows up. Very odd as the callsign that keeps popping up was just a lookup some time ago but seems to continue to propagate from the original lookup. I doubt?? it's the radio CAT file where the old callsign is coming from.

Did you try a clean install in case you have a corrupted file

Is any other program running?

This morning I reset the map cache which seems to be successful stopping the old callsign lookup from appearing in the logbook by default. Horray!