Cluster Announce Last QSO and Fldigi

[arcix]

I had just completed a PSK31 QSO using Fldigi.
RUMlog is configured to automatically fetch from Fldigi's logs, so I waited until the QSO appeared in RUMlog, then clicked on Ann. last logged QSO menu to spot the call. What appeared on the cluster wasn't that last QSO, but the previous one, an SSB contact I entered manually.

I'm using RUMlog 5.0.8

73, de Ulde IK2TYL

[DL2RUM]

Well, this is the way it works. Only a really logged QSO can be spotted vie this menu, not an imported QSO. In your scenario it is not useful, but this should prevent users to spot old QSOs.
How could I change this routine? Suggestions and good ideas are welcome.

[arcix]

Tom,

I thought that the announce last QSO function was intended to spot the most recent entry in the log, and I don't see why it should consider a QSO that was just received from Fldigi in a different way than a QSO I had entered directly in RUMlog.

Maybe a failsafe warning in case the QSO date/time is older than a few minutes could be a nice addition to the Ann. Last QSO function.

73,
Ulde IK2TYL

[K3DCW]

Tom,

I thought that the announce last QSO function was intended to spot the most recent entry in the log, and I don't see why it should consider a QSO that was just received from Fldigi in a different way than a QSO I had entered directly in RUMlog.

Maybe a failsafe warning in case the QSO date/time is older than a few minutes could be a nice addition to the Ann. Last QSO function.

73,
Ulde IK2TYL

Sorry for resurrecting a dead thread, but Tom asked for ideas on how to handle this. Ulde does raise a valid point...for those of us using Fldigi, an imported log probably shouldn't be treated any differently than a log entered directly into RULlog.

The problem is this: What if the logs were made 5 days ago and you are just now importing them? Obviously you don't want to auto-announce those.

One possible solution would be to have a setting in the Digi section to allow auto-spot of the last imported QSO **IF** it is imported from the Fldigi log (not from the Import ADIF function). Also, this should have a bit of logic...for example, no spotting of a QSO more than 5 minutes old (or some such limit).

Again, sorry for resurrecting a dead thread, but I can see the logic of Ulde's request.

73

Dave
K3DCW