aboutsummaryrefslogtreecommitdiffstats
path: root/src/plugins/python/pythonutils.cpp
diff options
context:
space:
mode:
authorMarcus Tillmanns <marcus.tillmanns@qt.io>2024-03-11 11:37:43 +0100
committerMarcus Tillmanns <marcus.tillmanns@qt.io>2024-03-14 09:22:01 +0000
commit685f452d91a4a733af5b9f9e3aff4a5e73ee37b2 (patch)
treec20af8b758f957d268b2e4dd157a3582cb978636 /src/plugins/python/pythonutils.cpp
parent1942506b2c84617a9d6f96df0f5b8421dc317c98 (diff)
SettingsDialog: Call Aspect::cancel on cancel
Previously the SettingsDialog did not call Aspect::cancel(). Without this, the volatile value is not reset if the user did some changes before pressing cancel. This "should" mean that re-opening the settings dialog should present the changed values again. But since not all aspects are implemented correctly, they reinitialize from their value instead of their volatileValue. When the Settings Dialog is reopened and applied, a warning is triggered as the container thinks its dirty, but the Aspect::apply returns false. Change-Id: I8fac66fc95f9118d69c789ced22481d121769f0b Reviewed-by: <github-actions-qt-creator@cristianadam.eu> Reviewed-by: Christian Stenger <christian.stenger@qt.io> Reviewed-by: hjk <hjk@qt.io>
Diffstat (limited to 'src/plugins/python/pythonutils.cpp')
0 files changed, 0 insertions, 0 deletions