RecentFiles kcm: whattoremember: Make the value visible in the UI match the value saved
In this commit: 1. Setting the property `kcfg_property=kcfg_value` on the QGroupBox. This should force the KConfigDialogManager to use that to retrieve that value that needs to be stored. 2. Introducing RecentFilesKcm::whatToRememberWidgetChanged which figures out the correct value of "what-to-remember" and sets it under the property `kcfg_value` and triggers the Save/Reset buttons. 3. Linking the above slot to the `QAbstractButton::clicked` signals of the radio buttons BUG: 397487 (cherry picked from commit 5f1b83a6)
-
I was building on kf5 for back-porting but it seems that
KCModule::setNeedsSave
does not exist in v5.102.0 (but exists in kf5). I will attempt to usemarkAsChanged
which does similar job.How would I test this? I am rebuilding everything on kf5 (which will take some time) and then planning to checkout kconfigwidgets:v5.102.0 and rebuild with --no-src - would that work as a test?
-
This needs to be reverted then, I did wasn't conscient this implied of KF version bump.
Edited by Méven Car -
mentioned in commit 9f524a6e
-
mentioned in merge request !1710 (closed)
-
How would I test this? I am rebuilding everything on kf5 (which will take some time) and then planning to checkout kconfigwidgets:v5.102.0 and rebuild with --no-src - would that work as a test?
You will need to reset --no-src build kcmutils with v5.102.0 as well.
Alternatively, we can revert it !1710 (closed).
-
The regression should be fixed with !1711 (merged)