Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

QLog 0.6.0, Settings: Modes #11

Closed
dl2ki opened this issue Mar 7, 2022 · 9 comments
Closed

QLog 0.6.0, Settings: Modes #11

dl2ki opened this issue Mar 7, 2022 · 9 comments
Labels
bug Something isn't working

Comments

@dl2ki
Copy link

dl2ki commented Mar 7, 2022

In the tab "Modes" you find 20 modes. Obviously the classic modes "CW", "LSB", "USB", "RTTY", "DATA" are missing. All available modes are "Disabled" for me, because they are not used.

This leads to the fact that when logging a CW QSO the mode cannot be selected in the QSO window. Whether an automatic takeover of the mode from the rig into the menu fields "Mode" / "Submode cannot be checked.

@foldynl
Copy link
Owner

foldynl commented Mar 7, 2022

That's strange. Unfortunately, I cannot confirm your finding. v.0.6.0 should have 44 modes where the mentioned modes are present. See screenshot from the release. Was there the same problem observed by you with the previous version (0.5.0)?

modes

@dl2ki
Copy link
Author

dl2ki commented Mar 7, 2022

Here is a screenshot of the window.

settings, modes

@foldynl
Copy link
Owner

foldynl commented Mar 7, 2022

Wow...Is it a result of upgrade from 0.5 to 0.6 or it's the same since you first used QLog ?

@foldynl
Copy link
Owner

foldynl commented Mar 7, 2022

Have you ever tried to edit a QLog database data file?

It doesn't make sense to me, because there is no patch that would break it like this. I also tried to deactivate and activate everything and I can't get the same state.

@foldynl
Copy link
Owner

foldynl commented Mar 7, 2022

Sorry for spamming.

I am continuing to investigate the issue but I have a workaround. The table is fully editable therefore you can redefine for example CHIP mode to CW with pre-defined Report format and DXCC should be CW/

@dl2ki
Copy link
Author

dl2ki commented Mar 7, 2022

Have you ever tried to edit a QLog database data file?

No.

Sorry for spamming.

I am continuing to investigate the issue but I have a workaround. The table is fully editable therefore you can redefine for example CHIP mode to CW with pre-defined Report format and DXCC should be CW/

No problem. I just tried this once and it seems to work. Tomorrow I will test this further.

According to my memory, this was also the case with version 0.5.0. I just uninstalled version 0.6.0 (purge), and reinstalled version 0.5.0. The settings menu looks the same for both versions.

The database is in the user directory and of course has not changed. I will backup and delete the database tomorrow and check it again.

@dl2ki
Copy link
Author

dl2ki commented Mar 8, 2022

I have uninstalled version 0.6.0 (purge) and backed up the database "qlog.db". After that I installed version 0.5.0.

After starting QLog the database is regenerated. The new file "qlog.db" has a size of 512,0 KiB.

The Modes menu looks like this:

v0 5 0_neueDatenbank

When the newly generated database is opened with "SQLite Studio", the content of the "modes, Indices" table looks like this:

v0 5 0_neueDatenbank_data

I can't say more about the database, as I have no experience with SQLite or other databases. I installed "SQLite Studio" yesterday only once to have a look at the contents of the database.

After an update to version 0.6.0 nothing changes in the new database.

@foldynl
Copy link
Owner

foldynl commented Mar 8, 2022

Thank you very much for detailed description.I am able to repeat it with the same result now.

@foldynl foldynl added bug Something isn't working and removed need more info labels Mar 8, 2022
foldynl added a commit that referenced this issue Mar 8, 2022
under special conditions, it could happen that the Modes table was not filled correctly.
The fix adds missing records and improve the filling of this table.
@foldynl
Copy link
Owner

foldynl commented Mar 8, 2022

Next release should repair the table.

@foldynl foldynl closed this as completed Mar 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants