Sugestions to better Log

[darknight-ux]

Please, if possible think about these new essential features:

• Choose where we can put the log database. Other HDs, partitions, etc. It is more safely.

• Automatic backup from database, with choose option of local save.

• Auto start rig control after open the program.

• Other possibility, was a portable version, without install.

I am using windows version.

[darknight-ux]

exclude this please, wrong account

[aa5sh]

Please, if possible think about these new essential features:

• Choose where we can put the log database. Other HDs, partitions, etc. It is more safely.

- you can do this although it isn't officially supported because it can cause problems but you can always create a SYM Link for the QLOG directory to be somewhere else.

• Automatic backup from database, with choose option of local save.

- This happens currently every 7 days.

• Auto start rig control after open the program.

- Look in the Activities section in the bottom status bar. You can have it autostart rig and rotor.

• Other possibility, was a portable version, without install.

I am using windows version.

73, Michael, AA5SH

[PY2AD]

Please, if possible think about these new essential features:

• Choose where we can put the log database. Other HDs, partitions, etc. It is more safely.

- you can do this although it isn't officially supported because it can cause problems but you can always create a SYM Link for the QLOG directory to be somewhere else.

Ok, I did it. But all logs have an option to save the database. Thats the ideia, not make a symlink. I asked some professional option.

• Automatic backup from database, with choose option of local save.

- This happens currently every 7 days.

Same of up, can choose when and where backup will done.

• Auto start rig control after open the program.

- Look in the Activities section in the bottom status bar. You can have it autostart rig and rotor.

Didn't find any option to autostart the rigs. Only manual option.

• Other possibility, was a portable version, without install.

I am using windows version.

73, Michael, AA5SH

[aa5sh]

Not sure why your installation wouldn't allow it to auto start with Activity Menu. Here is an another recent discussion where I put a few screenshots.
#724

[foldynl]

Ok, I did it. But all logs have an option to save the database. Thats the ideia, not make a symlink. I asked some professional option.

Personally, I don’t see a reason for it. QLog wants to take a different approach than other logs. QLog aims to shield the user from the technical details of how the application works. Whether the log is located here or somewhere else should not concern the user at all. However, it is QLog’s responsibility to keep this data consistent at all costs. If I let the user tinker with this, I cannot guarantee that.

Automatic backup from database, with choose option of local save.

• This happens currently every 7 days.
  Same of up, can choose when and where backup will done.

Again, I don’t see a reason for this. A regular user would leave this backup at the default value anyway. But the main point is that backups are not only made every 7 days, but also irregularly during database upgrades. QLog has this fully under control, and therefore I know what is included in each backup.

By the way, if the backup period doesn’t suit you, you can back up the entire directory with the database – its location depends on the platform, see the WIKI.

Other possibility, was a portable version, without install.

Can you please tell me what the benefit is? QLog installation process doesn't need anything special.

Didn't find any option to autostart the rigs. Only manual option.

See WIKI

[PY2AD]

Ok, I did it. But all logs have an option to save the database. Thats the ideia, not make a symlink. I asked some professional option.

Personally, I don’t see a reason for it. QLog wants to take a different approach than other logs. QLog aims to shield the user from the technical details of how the application works. Whether the log is located here or somewhere else should not concern the user at all. However, it is QLog’s responsibility to keep this data consistent at all costs. If I let the user tinker with this, I cannot guarantee that.

Its so easy to answer your question. When database is saved on the same partition of system, if system crashs, you loose your database. If we have options to choose, each user can save on your preference

Automatic backup from database, with choose option of local save.

• This happens currently every 7 days.
  Same of up, can choose when and where backup will done.

Again, I don’t see a reason for this. A regular user would leave this backup at the default value anyway. But the main point is that backups are not only made every 7 days, but also irregularly during database upgrades. QLog has this fully under control, and therefore I know what is included in each backup.

Same as database. Backup saved on the same place of database, isnt a backup. If looses 1, looses both. And yes, we can copy to other place, but is boring and not safely.Per example, if we can choose to make a bkp every time we closed the program, we guarantee the safe of databases.

By the way, if the backup period doesn’t suit you, you can back up the entire directory with the database – its location depends on the platform, see the WIKI.

Other possibility, was a portable version, without install.

Can you please tell me what the benefit is? QLog installation process doesn't need anything special.

Portable version can be used on a pen drive, very good to expeditions, SOTA, POTA, etc

Didn't find any option to autostart the rigs. Only manual option.

I found it, but not very easy to located. Could be more visible.

See WIKI

[foldynl]

Backup && DB.

QLog is a logging application, not a backup tool. It only prepares data for backup and keeps some history to guard against database migration issues or application errors.

You are correct that a backup on the same filesystem is not a real backup. However, as a responsible user, you are expected to use proper backup software for your documents; and QLog assumes you do. If you don’t, that’s your risk. If you do, then all QLog data resides on filesystems that are part of your regular backups.

Yes, a common reaction to this is that many logging applications have their own backup settings. But that’s a mistake. The backup of your data should properly be managed by a unified backup system, not by individual applications.

Portable version can be used on a pen drive, very good to expeditions, SOTA, POTA, etc

I still don’t understand why I should have a compact monolithic application. The only real issue I see is that QLog doesn’t have any synchronization between multiple instances. But this has already been discussed several times. I’m working on solving this, though it’s not an easy task. And yes, the common reaction is that many logs already have it. That’s true, but I want to implement it in a completely different way than usual.

I found it, but not very easy to located. Could be more visible.

Every user has different requirements. How else should this be visible other than in the documentation?