Poss minor bug in 1.23

[G4DWV]

Working with WSJT-X and JTAlert to interface with Log4OM. I like to have the 'Recent QSO' window showing (detached grid), just to be sure that the log entry gets made.

With 1.23 the entry does get made, but the window does not auto-refresh like it used to in previous versions; I have to manually refresh to see it.

Can the auto-refresh action be reinstated please?

73

[G4DWV]

Is this a minor bug or have I inadvertently changed a setting?

Mni tnx es 73,

Guy

[G4DWV]

Hi,

I have reverted to v1.22 and the auto-refresh behaviour is back.
Can this please be fixed in the next release?

Thanks

Guy

[G4DWV]

Knock, knock, knock!
Is anybody there?

[PB4FUN]

I just tried it and it refreshes normal.
So it might be something else (btw I do not have that window detached)

[G4DWV]

I just tried it and it refreshes normal.
So it might be something else (btw I do not have that window detached)

You would have to try both versions with the window detached to check the issue correctly. With all past versions the detached window auto-refreshes and with 1.23 it does not - that does point to where the issue lies until Lele or Terry chimes in.

It's really annoying as I have to click the window twice to see the logged QSO, once to give the window focus and the second time to refresh it.

Mni tnx es 73 de Guy G4DWV/4X1LT

[NN7D]

Hi Guy,

Since Terry is occupied, I'll take a stab at this. I just tested this on v1.23 with logging a qso in WSJT-X and JTAlert, with my Recent QSO window detached, and it updated both the Recent QSO (F8) tab and the detached Recent QSO window, without having to refresh anything. I am running Window 7, 64 bit. So not sure why it is not refreshing in your case. It is in mine.

Doug - W7DRM

[IW3HMH]

It's very strange, because the source of the QSO (manual or external source) will not have differences.
The main "issue" could be when an external software DIRECTLY INJECTS qso into Log4OM database. In that case Log4OM is not noticed about the activity (the database is an "external resource") and will react to changes only because something else triggers the database control.

Also statistics will not be updated in realtime when database changes from external events.
The "correct" way is to have Log4OM called to insert the QSO, if this is the case, because we've a couple of triggers that runs and keep the user interface aligned to the database informations

[G4DWV]

This is a puzzle indeed as it is completely reproducible here. I suppose I can work around it, but I do like to see my logged QSOs appearing in the log.

It is no that big an issue in the scale of things, but when it changes one's preferred chosen way of working an issue tends to assume more importance than it deserves .

Daniele, if you do decide to try to chase this up, I am happy to run any tests that you would like here. I backup daily (sometimes more often than that ) and I have no problems running risky code or doing anything 'dangerous' (at my own risk of course). I can even set up separate OS partitions for testing.

Mni tnx es 73 de Guy G4DWV/4X1LT

[G4DWV]

I have reverted to v1.22 as I *really* like the autorefresh.