From: Soeren Apel <[email protected]>
Since the application metadata is set in application.c,
we should use it instead of providing it manually every
time we create a QSettings object.
As I understand it, subclassing QApplication in application.c
is only a workaround for bad Qt behavior. In the event
that it is removed, the application metadata should be moved
so that persistent storage still works.
---
pv/application.cpp | 1 +
pv/mainwindow.cpp | 4 ++--
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/pv/application.cpp b/pv/application.cpp
index 224cc60..66991dd 100644
--- a/pv/application.cpp
+++ b/pv/application.cpp
@@ -28,6 +28,7 @@ Application::Application(int &argc, char* argv[]) :
{
setApplicationVersion(PV_VERSION_STRING);
setApplicationName("PulseView");
+ setOrganizationName("sigrok");
setOrganizationDomain("sigrok.org");
}
diff --git a/pv/mainwindow.cpp b/pv/mainwindow.cpp
index dae8f12..c3747e0 100644
--- a/pv/mainwindow.cpp
+++ b/pv/mainwindow.cpp
@@ -271,7 +271,7 @@ void MainWindow::setup_ui()
void MainWindow::save_ui_settings()
{
- QSettings settings("sigrok", "PulseView");
+ QSettings settings;
settings.beginGroup("MainWindow");
settings.setValue("state", saveState());
@@ -281,7 +281,7 @@ void MainWindow::save_ui_settings()
void MainWindow::restore_ui_settings()
{
- QSettings settings("sigrok", "PulseView");
+ QSettings settings;
settings.beginGroup("MainWindow");
--
1.7.8.6
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
sigrok-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
