https://bugs.kde.org/show_bug.cgi?id=508239
Igor Kushnir <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from Igor Kushnir <[email protected]> --- KConfigGroup::KConfigGroup(const KConfigBase *master, const QString &_group) sets KConfigGroupPrivate::bConst to true. I suspect the assertion has been failing since the ZoomController class was introduced many years ago, but no one has tested KDevelop with KF assertions enabled. When the KF assertions are disabled, the m_configGroup.sync() call in ZoomControllerPrivate::writeConfig() returns false and the zoom level is not updated in kdeveloprc until KDevelop exit. When I make KConfigGroup outerGroup non-const in StandardDocumentationView::initZoom(), m_configGroup.sync() returns true, and the assertion failure should be gone too. I am going to create a merge request with the fix soon. Too late for the 25.08.0 release unfortunately. Could be released in 25.08.1. On another note, the sync() call was ineffective, but no one has complained about losing zoom levels after a KDevelop crash. Syncing in one session does not affect another session until it is restarted. I wonder - should sync() be called each time something is written to config? Do you know about best practices? -- You are receiving this mail because: You are watching all bug changes.
