From 772552a441dae3ef7e25c7144269385c9ca68a4e Mon Sep 17 00:00:00 2001 From: Romain Forlot Date: Mon, 30 Apr 2018 23:59:35 +0200 Subject: Change when to notify The notify was in fact called 2 times. It is attended that a callback should "set" the signal value to record it. Setting the signal's value already call notify which an action should do at the end. Notifying has a meaning only if a signal value has been modified. Change-Id: I4a8128317a88bf7459b2c4aa0f575c4b2524e816 Signed-off-by: Romain Forlot --- signal-composer-binding/signal.cpp | 1 - 1 file changed, 1 deletion(-) (limited to 'signal-composer-binding/signal.cpp') diff --git a/signal-composer-binding/signal.cpp b/signal-composer-binding/signal.cpp index 0b17091..3a448b1 100644 --- a/signal-composer-binding/signal.cpp +++ b/signal-composer-binding/signal.cpp @@ -353,7 +353,6 @@ void Signal::onReceivedCB(json_object *eventJ) source.request = {nullptr, nullptr}; source.context = (void*)get_context(); onReceived_ ? ActionExecOne(&source, onReceived_, eventJ) : defaultReceivedCB(eventJ); - notify(); } /// @brief Make a Signal observer observes Signals observables -- cgit 1.2.3-korg