Skip to content

desktoppackage/configuration: track unsaved changes in shortcut configuration

The Shortcuts configuration page currently notifies the configuration dialog through the configurationChanged() signal that there are unsaved changes; this is not responsive to the user restoring the original configuration manually.

Instead, set the unsavedChanges property as appropriate. Along the way, we switch to the keySequenceModified signal, as captureFinished is deprecated.


unsavedChanges with setting an existing keyboard shortcut again is a bit weird (as there's a separate check and dialog for setting an already globally set shortcut, but it seems to work more or less as expected.

[patch that switched the page to use a FormLayout was removed, see !2938 (comment 1195789)]

Edited by Christoph Wolk

Merge request reports

Loading