Those of us who never stop the software...

[TecnoTalarn]

Hello ladislav
I am very happy with the latest version (0.45.0) of the software. The improvement of unifying the log sendings is a delight.

I would like to ask you for some improvements, at least for those of us who use the software continuously, without stopping it from one day to the next. The main reason is to have the Bandmap and alerts full, from the cluster.

When starting the program, the satellites, POTA/SOTA, etc. are updated. But I don't know if this update also occurs if the application is not closed. I think not.
It might be good, if it doesn't, for it to be done every 24 hours, for example...

And another thing, In my radio station the computer doesn't stop, but the radio does while I'm not in front of it. This causes the connection with the program to stop, and you have to reconnect manually.
My radios are connected via USB port, and the FLrig software is able to turn them on, They are an Icom 7300, and a Yaesu 710, and I think that maybe the program could be modified so that, instead of giving disconnection warnings, it waits for the new connection. Since I understand that the USB port does not really stop, otherwise it would not be possible to turn them on by program. I think this would be possible to do with most modern radios.

These are not urgent or necessary improvements, but I think many people would appreciate them, at least the "lazy" ones like me

Thanks
EB3AM

[oh2gba]

+1 for "the program could be modified so that, instead of giving disconnection warnings, it waits for the new connection. "

[foldynl]

When starting the program, the satellites, POTA/SOTA, etc. are updated. But I don't know if this update also occurs if the application is not closed. I think not.
It might be good, if it doesn't, for it to be done every 24 hours, for example...

QLog does not update these records once it is already running.

I think your use case is so extreme that there’s no real reason to do it differently for now. I recommend occasionally close QLog ;-)

the program could be modified so that, instead of giving disconnection warnings, it waits for the new connection

Unfortunately, you did not mentioned your QLog's Rig Setting. Do you use native FLRig Interface or Hamlib Flrig interface ? QLog' Hamlib Interface tries to recover from errors if the errors are "Soft errors". in case of "Hard error" it is not possible to recover and QLog emits the Error Dialog. Please, send me the error message and you QLog' Rig Setting.

[TecnoTalarn]

Well, the error I get is this one in the image.
With the Yaesu FT710 configuration
I'm using version 0.45.0 Flatpack.

I mentioned the FLRig as an example, since it is capable of turning on the radio.
I am connected to the radio via Hamlib directly.

As I said, it's not an emergency, but I think it could be useful.

About not closing the program?
It certainly should be done, but I do a few minutes of radio a day, not much, and from having the bandmap full to having nothing, it's like going back to the stone age.

73

[aa5sh]

What I often do is when I open QLog and I send a command to similar to 'SH/DX/100' or something even larger to get the recent spots.