[ABS] events: change method of launching app accepted/tizen/mobile/20160504.115343 submit/tizen_mobile_tpk/20160504.080735
authorl.stanislaws <l.stanislaws@samsung.com>
Wed, 4 May 2016 08:08:40 +0000 (17:08 +0900)
committerl.stanislaws <l.stanislaws@samsung.com>
Wed, 4 May 2016 08:08:40 +0000 (17:08 +0900)
commit64932709d7fbe3c4c58433bfad46ab0a4c36e979
treecb1b92ada7f8061648a4eb0d61654c7728eb7c17
[ABS] events: change method of launching app

After discussion with Aleksandr Sapozhnik we agreed that lockscreen
should not verify application launch request result, since its primary
task is to unlock screen, not launching application. Moreover there is
no guideline how lockscreen should handle failed launch requests.

Current logic has been modify in following manner:
1. If event do not support launching application or any error
   occured during launching, lockscreen will unlock immideatly
2. If app_control is launched successfully, lockscreen wait until
   APP_CONTROL_RESULT_APP_STARED or APP_CONTROL_RESULT_CANCELED events
   appear and unlock.

Issues: this way of unlocking do not enforce any synchronization method, so
        lockscreen may unlock before launched application appear.

Reference: submit/tizen/20160504.080735
Commit id: eb4ce69fdfb07df471ce2f41f62b347d6d94e840
Requested by: l.stanislaws@samsung.com
SDK rootstrap version: 20160503_2
org.tizen.lockscreen-0.1.0-arm.tpk [new file with mode: 0644]
org.tizen.lockscreen-0.1.0-i386.tpk [new file with mode: 0644]
packaging/org.tizen.lockscreen.spec [new file with mode: 0644]