Fix wrong behavior about return value of shortcut request accepted/tizen/3.0/common/20170214.180349 accepted/tizen/3.0/ivi/20170214.042507 accepted/tizen/3.0/mobile/20170214.042400 accepted/tizen/3.0/tv/20170214.042426 accepted/tizen/3.0/wearable/20170214.042446 submit/tizen_3.0/20170213.011824 submit/tizen_3.0/20170213.044947
authorseungha.son <seungha.son@samsung.com>
Fri, 10 Feb 2017 03:26:04 +0000 (12:26 +0900)
committerseungha.son <seungha.son@samsung.com>
Mon, 13 Feb 2017 00:53:23 +0000 (09:53 +0900)
commitd39f784cd5497fcbf3ea00155ad5efd21b7490f8
treee5dd157ae97a8c2e43a314512c5c75a2a8dbac4c
parentad352de6cf842eb66ae83bf0b794b0fafde81ed6
Fix wrong behavior about return value of shortcut request

 - Currently, It is a structure in which the caller can not get
   a proper return value when there is a request such as
   shortcut add or remove.
 - The handling for gdbus invocation has been modified so that
   caller can get proper return value.
 - related patch : https://review.tizen.org/gerrit/#/c/114090/

Signed-off-by: seungha.son <seungha.son@samsung.com>
Change-Id: I24a94d5d0d137e738ecc0fd332f2c2fa5f8e0fbf
include/shortcut_service.h
src/shortcut_service.c