You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SettingsCache::loadToSettings() restores the current values but if new keys have been added to the setting, it couldn't remove them.
Because of the internal cache used by Qt itself, using QSettings::clear()at the beginning of SettingsCache::loadToSettings() won't have any effect, even if QSettings::sync() comes after it.
I've encountered the problems caused by Qt's internal cache in one of my apps; they are very annoying. But GLib's Key-value file parser is completely reliable. So, I propose that we use it instead of QSettings in SettingsCache.
Context: I encountered the problem while fixing lxqt/lxqt#1513 (the reset button).
The text was updated successfully, but these errors were encountered:
SettingsCache::loadToSettings()
restores the current values but if new keys have been added to the setting, it couldn't remove them.Because of the internal cache used by Qt itself, using
QSettings::clear()
at the beginning ofSettingsCache::loadToSettings()
won't have any effect, even ifQSettings::sync()
comes after it.I've encountered the problems caused by Qt's internal cache in one of my apps; they are very annoying. But GLib's Key-value file parser is completely reliable. So, I propose that we use it instead of
QSettings
inSettingsCache
.Context: I encountered the problem while fixing lxqt/lxqt#1513 (the reset button).
The text was updated successfully, but these errors were encountered: