on xenial help sign in
Don't rely on changed signals from GSettings, they don't seem reliable
commitf87f8180a92b6c81e16365a1981bfee463f25963 authorMichael Terry <michael.terry@canonical.com> dateWed 19 Aug 2015, 19:24 (11 years ago) parent8f763f0
2 files changed+4−9
qml/Greeter/Greeter.qml+3−9 tests/mocks/GSettings.1.0/fake_gsettings.h+1
qml/Greeter/Greeter.qml+3−9
@@ -185,11 +185,6 @@ Showable {
185185 GSettings {
186186 id: greeterSettings
187187 schema.id: "com.canonical.Unity8.Greeter"
188− onChanged: {
189− if (key === "locked-out-time") {
190− forcedDelayTimer.checkForForcedDelay();
191− }
192− }
193188 }
194189
195190 Timer {
@@ -200,8 +195,8 @@ Showable {
200195 // for a few minutes. When we wake up, we want to quickly be correct.
201196 interval: 500
202197
203− property var delayTarget;
204− property int delayMinutes;
198+ property var delayTarget
199+ property int delayMinutes
205200
206201 function forceDelay() {
207202 // Store the beginning time for a lockout in GSettings, so that
@@ -216,9 +211,8 @@ Showable {
216211 // settings to keep the user out longer. But by storing
217212 // start-time, we never make the user wait longer than the full
218213 // lock out time.
219− // The code below that watches GSettings will pick up the change
220− // for us.
221214 greeterSettings.lockedOutTime = new Date().getTime();
215+ checkForForcedDelay();
222216 }
223217
224218 onTriggered: {
tests/mocks/GSettings.1.0/fake_gsettings.h+1
@@ -19,6 +19,7 @@
1919
2020#include <QList>
2121#include <QObject>
22+#include <QVariant>
2223
2324class GSettingsSchemaQml: public QObject
2425{