Qt 5.15.0 QSettings values not reloaded

[SGaist]

@ad5xj said in Qt 5.15.0 QSettings values not reloaded:

OK I think you are still not getting my question?

I do get it. However, it's usually simpler to debug code that uses objects properly just in case there's some additional stuff done in for example the destructor of said class which was never called in your case.

The next steps:

• ensure that the paths are indeed the same in both cases (you never know when doing string manipulation)
• check the content of the file (you likely already did)
• do the write and read as two explicit steps using for example two buttons to call the two methods separately.
• check the value of "name" on write
• check the content returned on read before applying the conversion to QString.

[ad5xj]

All of the mentioned items have been checked numerous times. If any of those applied the application would not load a correct value on a restart.

[SGaist]

Did you also try with the Qt version provided by your distribution ?

[ad5xj]

That is a giant step backward (v5.7).

[SGaist]

This is just to determine whether this one works correctly which your code.

[ad5xj]

Everything works correctly with my code EXCEPT this one thing. You mentioned earlier it could be an issue with the way QSettings caches values. Is there a way to flush and reload the values?

[Pablo J. Rogina]

@ad5xj said in Qt 5.15.0 QSettings values not reloaded:

Is there a way to flush and reload the values?

Documentation is your friend...

[ad5xj]

I think you will find that I do a sync() after each settings write. That is not the problem.

[SGaist]

Did you try to check the status of your QSettings ?

[ad5xj]

Again. EVERYTHING works as it should EXCEPT the new values do not appear until an application restart. Otherwise, the new values would not be stored and restored on restart.

[unficyp]

Did you ever find a solution to this ?
I'm on QT 5.15.2 and i have the same problem ?

[Christian Ehrlicher]

Please provide a minimal, compilable example to reproduce the problem. There is no report about such an issue in the bugtracker until now.