~aacid/gsettings-qt/use_qchar_upper

Force handling deferred delete events to avoid memory leaks Fixes: #1460970
Approved by: Nick Dedekind, Lars Uebernickel

added added

removed removed

GSettings {

id: settings

schema.id: "com.canonical.gsettings.Test"

// has to be "valueChanged" signal, not "changed"; the latter doesn't work reliably with the in-memory gsettings backend

onValueChanged: changes.push([key, value]);

}

onChanged: changes.push([key, value]);

SignalSpy {

id: changesSpy

target: settings

signalName: "changed"

}

GSettings {

function test_reset() {

settings.testInteger = 4;

settings.schema.reset('testInteger');

tryCompare(changesSpy, "count", 1); // this merely exists only to connect to the "changed" signal; resetting changes is async in gsettings

100

compare(settings.testInteger, 42);

101

}

102