e_appinfo: Delete E_Appinfo at compositor unbind instead of tzpol, tzlaunch_appinfo... 42/246242/4
authorJunseok, Kim <juns.kim@samsung.com>
Tue, 27 Oct 2020 07:35:38 +0000 (16:35 +0900)
committerJunseok, Kim <juns.kim@samsung.com>
Wed, 28 Oct 2020 10:44:36 +0000 (19:44 +0900)
commit5a0d39ac2b0410d07a9c2fbd7fddc9331aa599bb
tree049a40cb9548123db261098b6465adb58280ee8f
parent33d19a76c50b6e4dff2594b233bddf7b1b05fed6
e_appinfo: Delete E_Appinfo at compositor unbind instead of tzpol, tzlaunch_appinfo unbind.

The tizen_policy and tizen_launch_appinfo unbind can called by client when the client launching.
Since the E_Appinfo is removed at this time and re-created later, the base_output_resolution could not work properly.
For fix this issue, delete E_Appinfo when the compositor unbind callback called.

And added the E_Appinfo_Owner for recognize the E_Appinfo is created by client or server.
The E_Appinfo that created by client, will be destroyed at deregister_pid/appid request callback.
The others that created by server, will be destroyed at compositor unbind.

Change-Id: Id97ab328bc7a8a7ff97455d33f8b72c720b3b56b
Signed-off-by: Junseok, Kim <juns.kim@samsung.com>
src/bin/e_appinfo.c
src/bin/e_appinfo.h
src/bin/e_comp_wl.c
src/bin/e_policy_wl.c