aboutsummaryrefslogtreecommitdiff
path: root/autotests/kconfig_compiler/signals_test_no_singleton.kcfgc
diff options
context:
space:
mode:
authorAlex Richardson <arichardson.kde@gmail.com>2014-02-20 16:56:01 +0100
committerAlex Richardson <arichardson.kde@gmail.com>2014-02-20 18:14:24 +0100
commit6d3a4405fc2723f5796e845247b6b0eb0448216e (patch)
tree477c67a7c067ca1b74917bd244485998c8418623 /autotests/kconfig_compiler/signals_test_no_singleton.kcfgc
parent9e3d22c3f549b583eb60c958dd923bf7c5bf4586 (diff)
downloadkconfig-6d3a4405fc2723f5796e845247b6b0eb0448216e.tar.gz
kconfig-6d3a4405fc2723f5796e845247b6b0eb0448216e.tar.bz2
Make kconfig_compiler signals actually useful + add unit test
Previously the classes generated by kconfig_compiler would only emit the defined signals when using the setters provided by that class. However, when using e.g. KConfigDialog which uses KConfigSkeletonItem::setProperty() to change the items no signal was generated. This patch fixes this by using a wrapper KConfigSkeletonItem subclass that calls a private itemChanged() method in the generated class which updates the set of changed properties. As soon as the item is saved (usrWriteConfig() in the generated class is called) the signal will be emitted REVIEW: 115635 REVIEW: 115634
Diffstat (limited to 'autotests/kconfig_compiler/signals_test_no_singleton.kcfgc')
-rw-r--r--autotests/kconfig_compiler/signals_test_no_singleton.kcfgc9
1 files changed, 9 insertions, 0 deletions
diff --git a/autotests/kconfig_compiler/signals_test_no_singleton.kcfgc b/autotests/kconfig_compiler/signals_test_no_singleton.kcfgc
new file mode 100644
index 00000000..4d096e08
--- /dev/null
+++ b/autotests/kconfig_compiler/signals_test_no_singleton.kcfgc
@@ -0,0 +1,9 @@
+File=signals_test.kcfg
+ClassName=SignalsTestNoSingleton
+Singleton=false
+Mutators=true
+MemberVariables=private
+GlobalEnums=false
+UseEnumTypes=false
+ItemAccessors=false
+DefaultValueGetters=true