Set recent value to current value when callback is added 38/97138/3 accepted/tizen/common/20161114.171314 accepted/tizen/ivi/20161114.010412 accepted/tizen/mobile/20161114.010246 accepted/tizen/tv/20161114.010313 accepted/tizen/wearable/20161114.010342 submit/tizen/20161113.015118
authorKichan Kwon <k_c.kwon@samsung.com>
Fri, 11 Nov 2016 08:24:11 +0000 (17:24 +0900)
committertaeyoung <ty317.kim@samsung.com>
Sat, 12 Nov 2016 04:21:06 +0000 (13:21 +0900)
commitedd4a85f8f8b9d00b2a7fa7b8ffb658d90633231
tree88fc5ba639fbb4dbaac9c4bc8bc4760a33414906
parentd0ef3a27a664cd31c27d0e8c40c008963e83fc13
Set recent value to current value when callback is added

- Until now, initial recent value is NULL
- Therefore, when key is changed, callback always called
- It is usually correct, but we have to do exception handling
  - If value is set 0 -> 1, most keys are considered to be changed
  - But USB connection isn't changed (0,1=false, 2=true)

Change-Id: If78913539a4eb8c27dad5de40413e0edd5fc24ff
Signed-off-by: Kichan Kwon <k_c.kwon@samsung.com>
Signed-off-by: taeyoung <ty317.kim@samsung.com>
src/runtime_info.c