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

Do not save the settings twice #2182

Merged
merged 1 commit into from
Jun 23, 2024
Merged

Conversation

dforsi
Copy link
Contributor

@dforsi dforsi commented Jun 22, 2024

This PR removes a call to m_settings.save() in the destructor of MainWindow because the same call is made when handling the close event which happens just before the call to the destructor when terminating Sdrangel normally, as noted in #2107. When killing Sdrangel with Ctrl+C or similar, neither closeEvent nor ~MainWindow are called so the settings aren't saved anyway.

Settings are saved in MainWindow::closeEvent() which is called when Sdrangel
is exited by closing its main window, or when using the File/Exit menu (or
Ctrl+Q) or when pressing Alt+F4.
@f4exb f4exb merged commit 31c20df into f4exb:master Jun 23, 2024
2 of 3 checks passed
@dforsi dforsi deleted the fix/save-settings branch June 23, 2024 07:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants