Fix wrong behavior about return value of shortcut request accepted/tizen_3.0_common accepted/tizen_3.0_ivi accepted/tizen_3.0_mobile accepted/tizen_3.0_tv accepted/tizen_3.0_wearable accepted/tizen/3.0/common/20170214.180346 accepted/tizen/3.0/ivi/20170214.042506 accepted/tizen/3.0/mobile/20170214.042358 accepted/tizen/3.0/tv/20170214.042424 accepted/tizen/3.0/wearable/20170214.042445 submit/tizen_3.0/20170213.011824 submit/tizen_3.0/20170213.044947
authorseungha.son <seungha.son@samsung.com>
Fri, 10 Feb 2017 02:45:07 +0000 (11:45 +0900)
committerseungha.son <seungha.son@samsung.com>
Mon, 13 Feb 2017 00:52:06 +0000 (09:52 +0900)
commit6876496d509e132111e843a0daf8ed9df901a922
treec26017d9a659cf69f60ee535b4fcbd740fd60df1
parentb97fe420192994b46c5bf35bdae005ffc185de73
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 caller generates a request-id for each shortcut, passes the id
   to data-provider-master and passes the return vallue to caller
   using the id in the data-provider-master daemon.
 - related patch : https://review.tizen.org/gerrit/#/c/114091/

Signed-off-by: seungha.son <seungha.son@samsung.com>
Change-Id: I30791a7a1309df8d9473a373e785bdc9ceb1f62a
lib/src/shortcut_internal.c
lib/src/shortcut_manager.c