Solved Saving dial value
-
@rapid84
hi
the akey is the name of the value. It saves to registry so that why it needs a name
For you , it could be slidervalue or something that explains what u save.You can use anything u like for company. Its also because its store in registry.
So just use some name u like that IS not a real company. :) -
For loading i use;
QSettings settings("settingName"); int aValue=settings.value("aKey").toInt(); int aValue2=settings.value("aKey2").toInt(); ui->dial->setValue(aValue); ui->dial_2->setValue(aValue2);
and for saving i use
QSettings settings("settingName"); int somevalue = ui->dial->value(); int somevalue2 = ui->dial_2->value(); settings.setValue("aKey",somevalue); settings.setValue("aKey2",somevalue2);
These work for me , thanks for help. by the way, in a debian OS , where do it save ( in which directory)?
-
Hi
That is good question :)
try
qDebug() << settings.fileName(); -
If I may suggest one improvement is to use a better name than
"aKey" and "aKey2"
Maybe Dial1Value and Dial2Value -
when i click the close button, while it is saving data , it waits sometime and close with a 1-2 seconds delay. Is this normal ?
-
@rapid84
Normally it saves really fast so i never noticed it. -
@mrjj
on raspbian sometimes it takes up to 5 -6 seconds to store the data. i have tested it, maybe i will need to use QFile. -
@rapid84
ok. thats pretty long.
It must have a reason.
QFile should be faster. -
Hi,
You shouldn't need to but you can try adding a call to sync in order to flush the content of your settings to the disk.
-